Rancho RED OBSR rm 🦜Room serverObserver
How this repeater scores
CoreScope · relative to this mesh- Bridgeweight 0.300.00 × 0.30 = 0.000
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.63 × 0.25 = 0.158
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.00 × 0.20 = 0.000
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 is a room server, not a repeater
These four axes measure relaying, and passing other people’s traffic is not what a room server is for. A low grade here is close to meaningless as a judgement of it — it is being marked on somebody else’s exam.
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
38 samples · last 30 daysHistory 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.