Channel
@archive1333
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,019subscribers
-345 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003718060544 |
|---|---|
| Type | Channel |
| Username | @archive1333 |
| Created | 13 May 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/archive1333 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 20:54 | 4,019 | -21 |
| 30 Aug 2026, 06:32 | 4,040 | -42 |
| 26 Aug 2026, 22:55 | 4,082 | -43 |
| 24 Aug 2026, 02:57 | 4,125 | -37 |
| 20 Aug 2026, 18:46 | 4,162 | -55 |
| 17 Aug 2026, 10:57 | 4,217 | -57 |
| 13 Aug 2026, 13:28 | 4,274 | -42 |
| 10 Aug 2026, 22:51 | 4,316 | -35 |
| 8 Aug 2026, 06:30 | 4,351 | -13 |
| 7 Aug 2026, 14:02 | 4,364 | first reading |
8 posts held, back to 13 May 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5 pages 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 8 posts for this entry, the most recent from 22 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
626 reactions across 7 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👀 | 626 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 626 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 13 May 2026 to 22 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
ARCHIVE ENTRY #007 SOURCE: RESTRICTED MOUNTAIN COMPLEX the location does not appear on most recovered maps. access was unexpectedly granted. only one caretaker was present. no visitors. no staff. no activity. multiple abandoned structures were identified throughout the area. an empty hotel overlooking the mountains. closed facilities. unused roads disappearing into the forest. all operational records have…
👀64
ARCHIVE ENTRY #006 SOURCE: REDACTED LOCATION REPORT the location was discovered during a routine survey. it was unusually quiet. no wildlife. no wind. no electronic interference. several team members reported the same feeling: someone was already there. the coordinates were removed from all recovered records. we do not know who removed them. we only know that the site should not exist. multiple symbols ma…
👀50
ARCHIVE ENTRY #005 SOURCE: ANOMALOUS BURIAL RECORDS the location predates the earliest recovered transmissions. multiple structures were identified beneath the site. they do not appear on any official records. during the survey we recovered fragments containing the same symbol found in the broadcast terminal. the symbol should not exist here. the site is older than the signal itself. one recovered fragment co…
👀48
ARCHIVE ENTRY #004 SOURCE: ABANDONED BROADCAST TERMINAL the terminal was discovered beneath an abandoned structure. there was no power. there should not have been a signal. the device activated on its own. a transmission appeared on the screen. duration: 13 seconds. the footage contained symbols we have never recovered before. one frame contained a map. another contained a warning. the final frame containe…
👀53
ARCHIVE ENTRY #003 recovery speed increased unexpectedly. multiple users reported identical symbols appearing seconds before contact. we recovered at least 4 separate recordings. all of them contain different environments. the signal is spreading faster now. recovery progress: 32%
👀74
ARCHIVE ENTRY #002 SOURCE: UNKNOWN TRANSMISSION the signal does not behave like a normal broadcast. it appears in fragments. different people receive different pieces. some hear audio. some see symbols. some disappear shortly after contact. we still don’t know who sent it. recovery progress: 17%
👀104
ARCHIVE ENTRY #001 SOURCE: ABANDONED VALIDATOR NODES we found fragments hidden inside abandoned infrastructure. most files are corrupted. somebody tried to erase the project. they failed. restoring remaining fragments... 12%
👀233
Channel created
Showing the 8 most recent of 8 posts we hold for @archive1333. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“ARCHIVE//1333” (@archive1333), 4,019 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/archive1333.
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.