Channel
@TAGFESSARCHIVE
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
5subscribers
+4 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003678275079 |
|---|---|
| Type | Channel |
| Username | @TAGFESSARCHIVE |
| Created | 5 April 2026 — measured — dated from the channel’s first post |
| First recorded | 29 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/TAGFESSARCHIVE |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 24 Oct 2026, 19:27 | 5 | -1 |
| 17 Oct 2026, 04:10 | 6 | +2 |
| 10 Oct 2026, 03:17 | 4 | -1 |
| 29 Sept 2026, 19:15 | 5 | +3 |
| 8 Sept 2026, 08:00 | 2 | +1 |
| 29 Aug 2026, 19:00 | 1 | no change |
| 29 Aug 2026, 18:47 | 1 | first reading |
14 posts held, back to 5 April 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 14 posts for this entry, the most recent from 29 August 2026. An engagement rate over an empty window would be a number about nothing.
ㅤㅤㅤ @TAGFESS CURATEDLY, ☆ ... : UNLOCKED Hi Taggy, Tagfess udah open menfess nih! Sebelum kalian kirim menfess, pastikan dulu kalian sudah membaca rules untuk menjaga keamanan bersama ya. ○ BOT MENFESS : @TagFessBot ○ REPORT : @TagFessRobot SHOULD DO — HASTAGS MENFESS, SHOULDN'T DO, (&.. RUMUS USERNAME. : Let’s breathe…
Sticker, posted without a caption
Channel name was changed to «TAG FESS ARCHIVE.»
ㅤ 📮 (HELP FORWARD.) : OFFICIAL BASE USERNAME .. TELEGRAM ● @TAGFESS Tagfess hadir sebagai base username serbaguna. &. Tagfess juga mencantumkan hastag menfess yang gak kalah lengkap loh! Jadi, di bawah ini adalah contoh beberapa hastag yang ada di tagfess: 🛒 #BuyTag / #RentTag / #TradeTag .. Pencarian dan penawaran username. 🔎 #FindTag / #AskTag .. Pencarian jasa, admin/partner BA username, &. Ruan…
Sticker, posted without a caption
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 🛒 / ☆ THE NO-GO ZONE (SHOULDN'T DO) : ❎ 0.1 OOT (OUT OF TOPIC). Dilarang mengirim menfess yang tidak berkaitan dengan BA username, kecuali topik OOT pada hastag #RandomTag. Example: ❎ : Dia lucu banget deh ✅ : Dia lucu banget deh, sampe kelupaan bales buyer usn 😭 0.2 DORM RULES. Dilarang join Dorm TAGFESS apabila tidak menggunakan akun utama, tidak memakai foto profil, nama, username, dan b…
Sticker, posted without a caption
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ REGULATIONS &. ... STANDAR PROCEDURES. : In order to ensure that the Tagfess platform remains secure, transparent &. Conducive for all users. 🛒 / ☆ THE STANDARD (SHOULD DO) : ✅ 0.1 WAJIB JOIN @TAGFESS, terlebih dahulu. 0.2 DORM RULES &. KETENTUAN AKUN. Wajib menggunakan akun utama dengan memakai foto profil, nama, username, dan bio yang jelas! Serta mencantumkan type acc pada bio, j…
Sticker, posted without a caption
ㅤ BEHIND THE EVOLUTION OF USERNAME BASE &. (T.F. 6. 8.0) 2026, 26. 🛒⚡️ @TAGFESS. “.. A Decidated Community Identity &. Space Ready to Cater All Your Needs ..” ••• We have created a versatile space, specially curated to resemble a shared hub &. Cater to users’ sensibilities. A sanctuary poised to blur …
Sticker, posted without a caption
RUMUS USERNAME: @RUMUSUSERNAMES/@RUMUSUSNS
Showing the 12 most recent of 14 posts we hold for @TAGFESSARCHIVE. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“TAG FESS ARCHIVE.” (@TAGFESSARCHIVE), 5 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/TAGFESSARCHIVE.
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.