ChatterBack🔍Join
States/North Carolina/MeshCore/Danbury Repeater
MC

Danbury RepeaterRepeater

5cd26c52dcf6 · North Carolina
● Heard 4 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.42 / 1.00
C is 0.30 and above. 0.45 would make it B.
249
relayed · 24 h
  • Bridgeweight 0.300.22 × 0.30 = 0.065

    How much of the mesh has to pass through it. A chokepoint between two halves of a network scores high.

  • Coverageweight 0.250.44 × 0.25 = 0.110

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

  • Redundancyweight 0.250.19 × 0.25 = 0.048

    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 12 of the 12 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.

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
Neighbours21–4

Node

from the mesh, refreshed every few hours
Protocol
MeshCore
Node ID
5cd26c52dcf6
Role
Repeater
Hardware
-
Preset
-
Channel
-
Firmware
-
Neighbors
2
Relayed 24 h
249
Adverts seen
239
Coverage
0.44
Usefulness
C · 0.42
First seen
2026-06-01