🟢RPTR05Repeater
How this repeater scores
CoreScope · relative to this mesh- Bridgeweight 0.300.73 × 0.30 = 0.218
How much of the mesh has to pass through it. A chokepoint between two halves of a network scores high.
- Coverageweight 0.250.39 × 0.25 = 0.097
How much of the mesh it can reach, weighted so near neighbours count more than distant ones.
- Redundancyweight 0.250.00 × 0.25 = 0.000
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.19 × 0.20 = 0.038
How much it actually relayed, measured rather than inferred from the map. It is carrying little traffic compared with the busiest repeater here.
What would actually change this
- This one is well sited
It out-reaches 27 of the 27 repeaters within 25 miles, which average 0.12. If the grade is still low, that is about position in the network rather than anything the radio is doing wrong.
- Redundancy at zero is good news
It means something else already covers this node’s job, so losing it would not split the mesh. Raising this number would mean making the network more fragile. It is the one figure here nobody should chase.
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.