tomf₃ 🤘 ObsevRepeaterObserver
How this repeater scores
CoreScope · relative to this mesh- Bridgeweight 0.300.01 × 0.30 = 0.004
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.47 × 0.25 = 0.118
How much of the mesh it can reach, weighted so near neighbours count more than distant ones.
- Redundancyweight 0.250.13 × 0.25 = 0.032
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.200.35 × 0.20 = 0.071
How much it actually relayed, measured rather than inferred from the map.
What would actually change this
A low grade on a repeater that works fine usually means the area is well served, not that the machine is bad. Over half the weight — Bridge and Redundancy — describes where it sits among its neighbours, and neither is yours to move.
- This one is well sited
It out-reaches 83 of the 101 repeaters within 25 miles, which average 0.16. 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.