ChatterBack🔍Join
States/Nevada/MeshCore/Ophir {lora.sh}
MC

Ophir {lora.sh}Repeater

fe3beb42dd17 · Nevada
● Heard 11 h agovia map.nvme.sh
Position as last reported by the node. Members’ own nodes can be shown at grid precision instead.

How this repeater scores

CoreScope · relative to this mesh
B
0.49 / 1.00
B is 0.45 and above. 0.65 would make it A.
372
relayed · 24 h
  • Bridgeweight 0.300.15 × 0.30 = 0.045

    How much of the mesh has to pass through it. A chokepoint between two halves of a network scores high. Traffic has other ways round. Not a fault - it means the area is well connected.

  • Coverageweight 0.250.79 × 0.25 = 0.196

    How much of the mesh it can reach, weighted so near neighbours count more than distant ones.

  • Redundancyweight 0.250.18 × 0.25 = 0.045

    What breaks if it vanishes. High means nothing else covers its job. Something else already covers what it does, so losing it would not split the mesh.

  • Trafficweight 0.201.00 × 0.20 = 0.200

    How much it actually relayed, measured rather than inferred from the map.

What would actually change this

  • This one is well sited

    It out-reaches 50 of the 51 repeaters within 25 miles, which average 0.30. If the grade is still low, that is about position in the network rather than anything the radio is doing wrong.

  • A low Bridge is not a fault

    Bridge measures how much traffic has no choice but to pass through this node. It falls when neighbours put up repeaters that cover the same ground — so it can drop without anything changing here at all. There is nothing to tune.

Every axis is scored against the other repeaters this analyzer can see, so 1.00 means “the best of these” rather than perfect, and a grade here is not comparable with one from another mesh. CoreScope’s own note on the bands is that they are a first cut, not tuned against real data — so treat the letter as a rough impression and the number as the real answer.

History

47 samples · last 30 days
Neighbours3831–38

Node

from the mesh, refreshed every few hours
Protocol
MeshCore
Node ID
fe3beb42dd17
Role
Repeater
Hardware
-
Preset
-
Channel
-
Firmware
-
Neighbors
38
Relayed 24 h
372
Adverts seen
70
Coverage
0.79
Usefulness
B · 0.49
First seen
2026-09-10