ChatterBack🔍Join
States/Minnesota/MeshCore/🌹🏢
MC

🌹🏢Repeater

2e10db6d75ff · Minnesota
● Heard 3 h agovia corescope.mspmesh.org
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
A
0.67 / 1.00
A is 0.65 and above.
196
relayed · 24 h
  • Bridgeweight 0.300.22 × 0.30 = 0.066

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

  • Coverageweight 0.250.89 × 0.25 = 0.223

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

  • Redundancyweight 0.251.00 × 0.25 = 0.250

    What breaks if it vanishes. High means nothing else covers its job.

  • Trafficweight 0.200.68 × 0.20 = 0.135

    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 95 of the 100 repeaters within 25 miles, which average 0.46. 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

46 samples · last 30 days
Neighbours7557–75

Node

from the mesh, refreshed every few hours
Protocol
MeshCore
Node ID
2e10db6d75ff
Role
Repeater
Hardware
-
Preset
-
Channel
-
Firmware
-
Neighbors
75
Relayed 24 h
196
Adverts seen
26
Coverage
0.89
Usefulness
A · 0.67
First seen
2026-08-26