RULES BOOST 🖤 CHAT 👠 VIDEO CHANNEL

Channel
e̶̶t̶̶e̶̶r̶̶n̶̶a̶̶l̶ space
@eternalspaceep
On this record: Topic · Growth · Engagement · Posts · Cite this entry
193subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003723000838 |
|---|---|
| Type | Channel |
| Username | @eternalspaceep |
| Created | 19 February 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/eternalspaceep |
Topic
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 11:39 | 193 | -6 |
| 13 Sept 2026, 17:02 | 199 | +28 |
| 6 Sept 2026, 08:40 | 171 | -5 |
| 28 Aug 2026, 20:36 | 176 | -4 |
| 22 Aug 2026, 13:33 | 180 | -9 |
| 14 Aug 2026, 06:13 | 189 | -1 |
| 8 Aug 2026, 12:01 | 190 | no change |
| 7 Aug 2026, 19:21 | 190 | first reading |
Engagement
8 posts held, back to 19 February 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 8 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Sticker, posted without a caption
Перед тем как вступать в кф прочитайте правила, а потом подавайте заявку
Sticker, posted without a caption
Администрация Владелец- @Lollataao Совлд- @Pri4vas Админы по чату- Луис Админы по нью- По вливу-Роуз Админы по видео- По активу-
Sticker, posted without a caption
норма: в день 35 в неделю 150 рест можно брать максимум на месяц, по поводу реста писать владельцу. уважать администрацию и всех участников кф. оскорбления можно только в шутку, но шутка для всех должна быть шуткой.Маты разрешены спам/использование калла/любая реклама без разрешения одного из администраторов запрещена. вышли из кф без уважительной причины или не предупредив-бан рж запрещено. расчленёнка/насили…
Channel created
Showing the 8 most recent of 8 posts we hold for @eternalspaceep. 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.
Cite this entry
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“e̶̶t̶̶e̶̶r̶̶n̶̶a̶̶l̶ space” (@eternalspaceep), 193 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/eternalspaceep.
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.