ChatterBack🔍Join
States/North Carolina/MeshCore/😎 KQ4HLZ tester
MC

😎 KQ4HLZ testerRepeater

a6ccc2a60e85 · North Carolina
Last heard 25 h agovia analyzer.nashme.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
C
0.30 / 1.00
C is 0.30 and above. 0.45 would make it B.
1852
relayed · 24 h
  • Bridgeweight 0.300.00 × 0.30 = 0.001

    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.39 × 0.25 = 0.098

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

  • Redundancyweight 0.250.02 × 0.25 = 0.006

    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 67 of the 99 repeaters within 25 miles, which average 0.21. 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.

  • 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.

History

47 samples · last 30 days

History starts from today. Readings were only ever stored as a single latest value before now, so there is nothing earlier to show — trends will fill in as the mesh is sampled.

Node

from the mesh, refreshed every few hours
Protocol
MeshCore
Node ID
a6ccc2a60e85
Role
Repeater
Hardware
-
Preset
-
Channel
-
Firmware
-
Neighbors
-
Relayed 24 h
1852
Adverts seen
15
Coverage
0.39
Usefulness
C · 0.30
First seen
2026-09-12