![Telegram profile photo for EDGE EMBY.STAR.CORE [REDACTED]](https://cdn.tgregister.com/av/ac/acee47245e14ed56192086f89e191122303a1de007fd7635501850781fc97c9b.jpg)
Channel
@edge_emby
On this record: Topic · Growth · Engagement · Posts · Cite this entry
885subscribers
+22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002894400566 |
|---|---|
| Type | Channel |
| Username | @edge_emby |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/edge_emby |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 92% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 07:02 | 885 | -8 |
| 18 Sept 2026, 21:58 | 893 | -1 |
| 10 Sept 2026, 05:15 | 894 | +5 |
| 31 Aug 2026, 02:37 | 889 | +1 |
| 24 Aug 2026, 21:44 | 888 | +32 |
| 16 Aug 2026, 19:44 | 856 | -6 |
| 8 Aug 2026, 13:15 | 862 | -1 |
| 8 Aug 2026, 01:17 | 863 | no change |
| 7 Aug 2026, 16:55 | 863 | first reading |
4 posts held, back to 3 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 26 June 2026. An engagement rate over an empty window would be a number about nothing.
CAS.TERM // NODE: STAR.CORE > [SYS] COMM_LINK // STATUS: DIAGNOSTIC_MODE > [LOG] Querying prior session anomalies... > [██ FATAL ██] MAIL_SUBSYSTEM_CRASH (ERR_0xOVERFLOW) > [INIT] Bootstrapping recovery sequence... > [MODULE] Flushing corrupted registry cache... [OK] > [MODULE] Re-allocating secure bandwidth... [OK] > Rebuilding communication bridge: > ████████████████████ [ 100% ] [===============================…
// RECOVERED TRANSMISSION : PARTIAL ========================================= SOURCE [ STAR.CORE ] UPLINK [ ESTABLISHED ] ARCHIVE [ SYNCHRONIZED ] ACCESS [ ██████ / ENCRYPTED ] > init://uplink.sys ............... [OK] > mount://media.archive ........... [OK] > wake://star.core ................ [ONLINE] > open://enrollment.channel ....... [READY] [CORRUPTED MANIFEST] 53 54 41 52 2E 43 4F 52 45 0xD…
Channel photo updated
Channel name was changed to «EDGE EMBY.STAR.CORE [REDACTED]»
Showing the 4 most recent of 4 posts we hold for @edge_emby. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 4 October 2026 — this entry's latest reading, not the date you are reading this.
“EDGE EMBY.STAR.CORE [REDACTED]” (@edge_emby), 885 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/edge_emby.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.