RELAY4offline 59d
!49b3d374CLIENTHELTEC_V4
Identity
self-reported- Long name
- RELAY4
- Short name
- d374
- Node ID
- !49b3d374 (1236521844)
- Role
- CLIENT
- Hardware
- HELTEC_V4
- Firmware
- -
- Licensed
- no
- First heard
- Aug 23, 2026, 12:24:04
- Last heard
- Aug 25, 2026, 18:10:29
- Public key
- -
First heard
Aug 23, 2026, 12:24:04
Last heard
59d ago
Packets / receptions
7 / 7
Position
unknown
Nearby (direct links)
Loading nearby nodes…
What it transmits (14d)
No packets in the window.
On network 62 days~0 packets/day
Activity (day x hour, America/Chicago)
Sun
Mon
Tue
Wed
Thu
Fri
Sat
0h6h12h18h23h
Recent messages
This node has not sent observed text.
Reliability & reach
Heard direct
0%
Gateways
3
Brokers
3
Farthest direct
-
Uptime
-
Chattiness
57%ile
Advertisements (7d)
0
ChannelsLongFastPKI
RF neighbor graph
green = this node hears them; amber = they hear this node.
Uptime & availability
Avail 24h
0%
Avail 7d
0%
Avail 30d
0%
Uptime
-
Reboots 30d
0
Longest run
-
Heard, hourly (7d)no reboot in 30d
heard no dataoldest left, newest right
Biography
- Aug 23, 2026, 12:24:04roleCLIENT
- Aug 23, 2026, 12:24:04hw_modelHELTEC_V4
- Aug 23, 2026, 12:24:04short_named374
- Aug 23, 2026, 12:24:04long_nameRELAY4
Best gateways (advisor)
Ranked by reception quality and consistency. Use this to spot redundant coverage and gaps.
| Gateway | Status | Direct | Relayed | Avg RSSI | Avg SNR |
|---|---|---|---|---|---|
| !50f51e93 | relayed | 0 | 3 | - | - |
| !aca9db50 | relayed | 0 | 1 | - | - |
| !f661aa40 | relayed | 0 | 3 | - | - |
Traffic fingerprint
Profile: insufficient data0 receptions, UTC hours
| 0 | 6 | 12 | 18 | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sun | ||||||||||||||||||||||||
| Mon | ||||||||||||||||||||||||
| Tue | ||||||||||||||||||||||||
| Wed | ||||||||||||||||||||||||
| Thu | ||||||||||||||||||||||||
| Fri | ||||||||||||||||||||||||
| Sat |