Channel
@jarakolll
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003962133192 |
|---|---|
| Type | Channel |
| Username | @jarakolll |
| Created | Between 1 April 2026 and 4 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jarakolll |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 11:16 | 1 | no change |
| 13 Aug 2026, 18:00 | 1 | first reading |
14 posts held, back to 4 May 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 pageof 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 8 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Collaboration 👍 @BizOrion with @arakolskie
archive Ara kol pinned «UNION RULES подписка 1:1 — 5:5 союз от 0+ Папка: рп, в редком случае рп + актив. рп в понедельник, среду, пятницу. рп будет держаться 30 минут, важные час. союзы заключаем с кланами/семьями/исд/обычные каналы. посты не делаем сразу в союз лист. …»
File, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
File, posted without a caption
Photo, posted without a caption
File, posted without a caption
Photo, posted without a caption
File, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 14 posts we hold for @jarakolll. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“archive Ara kol” (@jarakolll), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/jarakolll.
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.