6 Jul 2026, 15:48 UTC48 viewsread 9 August 2026
набор
Channel
анлупчики переезд
@unloop_oi1
On this record: Growth · Engagement · Posts · Citations · Cite this entry
98subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003894190589 |
|---|---|
| Type | Channel |
| Username | @unloop_oi1 |
| Created | Between 1 February 2026 and 29 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/unloop_oi1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 06:11 | 98 | no change |
| 9 Aug 2026, 22:32 | 98 | first reading |
Engagement
19 posts held, back to 29 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 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 19 posts for this entry, the most recent from 6 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
6 Jul 2026, 15:48 UTC37 viewsread 9 August 2026
Forwarded from @unloop_oiPhoto
🎀🎪 Nᧉωs ❌ 𝔘nlσ𐐫p.📰· —·➖·➿· 🎀 ·➿·➖·— 미친 💧 * wᧉ 𐐼ִrᧉ ʋnch𝐢l𝕕 · 🎀 υᩛׄ н𐐼с для в𐐼с нᨷв𐐫сти, к сᨷж𐐼лᧉнию нᧉ 𐐫чень кр𐐼с𐐫чныᧉ, н𐐼ш𐐼 любим𐐼я с𐐼ш𐐼 к огр𐐫мн𐐫мυᩛׄ сож𐐼лᧉнию п𐐫кинул𐐼 грυᩛׄппу п𐐫 личным причин𐐼м, жᧉл𐐼ем ей уд𐐼чи и υᩛׄспех𐐫в в д𐐼льнᧉйшем. а т𐐼кже 𐐫ткрываем п𐐫 эт𐐫й причинᧉ н𐐼бор н𐐼 н𐐫вую υᩛׄч𐐼стницу с прот𐐫типом хики . / ❌ 𝐓𝗋ʋᧉ 🤩 #𝐔nlꪮop. —·➖·➿· 🎀 ·➿·➖·— . · 🤡· @unloop_oi !! . · пр𐐼вил𐐼 и 𐐼нкет𐐼 бυᩛׄд
2 Jul 2026, 08:11 UTC63 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
2 Jul 2026, 08:11 UTC54 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
1 Jul 2026, 03:15 UTC37 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
1 Jul 2026, 03:15 UTC30 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
30 Jun 2026, 16:17 UTC25 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
30 Jun 2026, 16:17 UTC27 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
30 Jun 2026, 16:17 UTC26 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
30 Jun 2026, 16:17 UTC21 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
30 Jun 2026, 16:17 UTC19 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
30 Jun 2026, 16:17 UTC22 viewsread 9 August 2026
ПЕРЕЕЗД https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi https://t.me/unloop_oi
Showing the 12 most recent of 19 posts we hold for @unloop_oi1. 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.
Citation-graph rank
Citation-graph rank — 54,308 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“анлупчики переезд” (@unloop_oi1), 98 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/unloop_oi1.
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.