Sticker, posted without a caption

Channel
𝕴𝐍𝐅𝕺 › 𝐀𝕯𝐋𝕰𝐑𝐌𝕬𝐍
@Adlerman_info
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
228subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003039381483 |
|---|---|
| Type | Channel |
| Username | @Adlerman_info |
| Created | 10 September 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/Adlerman_info |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 19:23 | 228 | +1 |
| 8 Aug 2026, 10:19 | 227 | no change |
| 8 Aug 2026, 06:53 | 227 | first reading |
Engagement
11 posts held, back to 10 September 2025 — 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.
- ERR · 30 days
- 231.3%
- avg views ÷ 228 subscribers
- Avg views / post
- 527
- 10 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 10
- of 11 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 11 (10 September 2025 – 27 July 2026) |
| Views total | 5,273 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:19 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
. ࣪ 🅰️. 𝐀𝐌𝕴𝐋𝐘 𝐑𝐄𝕮𝐑𝐔𝕴𝐓𝐌𝕰𝐍𝐓 🎀 ㅤ . . 𝐀𝖽𝗅𝖾𝗋𝗆𝖺𝗇 𝖿𝖺𝗆𝗂𝗹𝗒 𝐚𝗅𝗐𝖺𝗒𝗌 𑄜𝗉𝗲𝗇𝗌 𝗂𝘁𝗌 𝐝𝗈𝗈𝗋𝗌 𝗍𝗈 𝗇𝗲𝗐 𝐟𝖺𝗆𝗂𝗹𝗒 𝐦𝖾𝗆𝖻𝖾𝗋𝗌 ㅤㅤ 🤩Статус набора: открыт. ㅤ Перед вступлением не забудьте ㅤ поставить фамилию в профиль. ㅤ 𝑫𝖾 ︩︪ׄ𝐀𝖽𝗅𝖾𝗋𝗆𝖺𝗇 𝐀𝖽𝗅𝖾𝗋︩𝗆𝖺𝗇 𝕬𝖽𝗅𝖾𝗿𝗆𝖺𝗇 ㅤㅤ. . Анᴋᴇᴛу ᴏᴛᴨᴩᴀʙᴧяᴛь в бота.
Sticker, posted without a caption
ㅤㅤ . ࣪ 🅰️. 𝐍𝐈𝕺𝐍𝐒 𝐅𝐀𝐌𝕴𝐋𝐘 🎀 ㅤ . . 𝐀𝗅𝗅𝗂𝖺𝗇𝖼𝖾𝗌 𝖻𝖾𝘁𝗐𝖾𝖾𝗇 𝐤𝗂𝗇𝗀𝖽𑄜𝗆𝗌 𝖺𝗿𝖾 𝐚𝖻𑄜𝗎𝗍 𝗰𝗈𝗈𝗉𝖾𝗋𝖺𝗍𝐢𝗈𝗇 𝐚𝗇𝖽 𝐬𝗎𝗉𝗉𝗈𝗋𝗍 𝗶𝗇 𝖽𝗂𝖿𝖿𝗂𝖼𝘂𝗅𝗍 𝐭𝗂𝗆𝖾𝗌. ㅤㅤ ㅤ ㅤ« . . 𝕺бщее право союз𑄜в » ㅤ𝐕𝖺𝗇𝖼𝖾 • каналㅤㅤ 𝐃𝖺𝗇𝖿𝖾𝗋 • канал ㅤㅤ ㅤㅤ 𝐊𝖺𝗆𝗂𝗌𝗁𝗂𝗋𝗈 • канал ㅤㅤ(🕯 ) 𝐇ᴀɯи ᴄ𑄜юɜниᴋи (семьи): 𝟏. ○ ᪾ 𞋯ᰰ⃜𓈒 𝕭𝐄𝐋𝐋𝐄𝕽𝕺𝕾𝕰 𝐅𝐀𝐌ᏐᏓᎽ 𝂅ׄ ๋ ࣭ 𝟐. @BelleroseFamily 𝟏. 𝐋𝐎𝐑✶𝐍𝐓𝟏𝐍𝐄 𝟐. @L0R4NT1N_info
Sticker, posted without a caption
ㅤ . ࣪ 🅰️. 𝕬𝐌𝕴𝐋𝐘 𝐇𝕴𝐒𝐓𝕺𝐑𝐘 🎀 ㅤ . . 𝐄ach fam𝗶ly 𝐡as i𝘁s 𑄜wn hist𑄜ry wh𝗶ch 𝐠oes ba𝗰k deep 𝗶nt𑄜 ant𝗶quity. 𝐎ur fam𝗶ly is n𑄜 𝐞xcepti𑄜n.
Sticker, posted without a caption
ㅤ . ࣪ 🅰️. 𝐀𝐌𝕴𝐋𝐘 𝐌𝕰𝐌𝐁𝕰𝐑𝐒 🕯 ㅤ . . 𝐀 𝗋𝖾𝗌𝗽𝖾𝖼𝗍𝖾𝖽 𝐟𝖺𝗆𝗂𝗅𝗒, 𝖺𝖻𑄜𝗎𝗍 𝗐𝗁𝗶𝖼𝗁 𝐭𝗁𝖾𝗋𝖾 𝖺𝗋𝖾 𝗌𑄜 𝗆𝖺𝗻𝗒 𝐝𝗂𝖿𝖿𝖾𝗋𝖾𝗇𝗍 𝗄𝗂𝗇𝖽𝗌 𑄜𝖿 𝐫𝗎𝗺𝗈𝗋𝗌. ㅤㅤ «𝐃𝕬𝐍𝐅𝕰𝐑 🎀 𝐂𝕬𝐒𝐒𝐈𝕰𝐋» — Правители управляют судьбой всей семьи и несут огромную ответственность, однако именно поддержка ближайшего круга позволяет удержаться у власти. ㅤㅤ ㅤㅤ ㅤ «𝐍𝕴𝐊𝐎 🎀 𝐌𝕺𝐍𝐓𝐇» — Одни из самых приближённых людей в семье к народу и домочадцам. ㅤ ㅤ ㅤㅤ «𝐇𝕴𝐃𝕰𝐌𝖄 🎀 𝐒𝕺𝐌𝐈» ㅤㅤ ㅤㅤ ㅤㅤ«𝐊𝕬𝐑…
Sticker, posted without a caption
ㅤㅤ . ࣪ 🅰️. 𝐀𝐕𝕴𝐆𝐀𝐓𝗜𝕺𝐍 🎀 ㅤ . . 𝐓𝗁𝖾 ρ𝘂𝗯𝗅𝗂𝖼 𝐯𝐢𝖾𝗐𝗌 т𝗁𝖾 𝗋𑄜𝗒𝖺𝗅 𝗳𝖺𝗆𝗂𝗅𝗒 𝗇𑄜𝗍 𝗮𝘀 𝐢𝗻𝖽𝗂𝗏𝗂𝖽𝗎𝖺𝗅𝗌, 𝐛𝘂т 𝖺𝗌 𝖾т𝖾𝗋𝗇𝖺𝗅 𝗌𝗒𝗆𝖻𑄜𝗅𝗌. 𝕴𝖿 т𝗁𝖺т 𝗌𝗒𝗆𝗯𑄜𝗅𝗌 𝖼𝗋𝖺𝖼𝗄𝗌, 𝖿𝖺𝗂т𝗁 𝐢𝗇 тн𝖾 𝗌т𝖺т𝖾 𝐰𝗂𝗅𝗅 𝖼𝗋𝗎𝗆𝖻𝗅𝖾. ⎯ 𝟎𝟏 . 𝐑𝖀𝕷𝐄𝐒 › пραвила ⎯ 𝟎𝟐 . 𝐌𝕰𝗠𝗕𝐄𝐑𝐒 › члены семьи ⎯ 𝟎𝟑 . 𝐇𝐈𝕾𝗧𝕺𝐑𝐘 › истσρия семьи ⎯ 𝟎𝟒 . 𝐑𝐄𝕮𝗥𝗨𝕴𝐓𝐌𝗘𝗡𝐓 › набор ⎯ 𝟎𝟓 . 𝐔𝗡𝐈𝕺𝐍𝐒 › союзы ㅤ . . 𝐀𝐑𝕮𝗛𝗜𝐕𝐄 : 𝐋𝗜𝕱𝐄 : 𝐁𝔒𝕺𝐒𝐓 : 𝐁𝕺𝐓 ㅤㅤ . . 𝐓𝗜𝐊 - 𝐓𝕺𝗞 : 𝐄𝐗 . 𝐂𝗛𝕬𝐓
Channel created
Showing the 11 most recent of 11 posts we hold for @Adlerman_info. 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 — 30,345 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.
Mentions
Named by 24 registered channels — 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.
@adi_flood_life · 1891 postUNIONS / 𝐵𝑒𝓁𝓁𝒶𝒹𝑜𝓃𝓃𝒶 𝒻𝓁𝑜𝑜𝒹
@BELLADONNAUNION · 111 post𝐔𝐍𝐈𝐎𝐍𝐒 | 𝐂𝐀𝐑𝐏𝐄 𝐃𝐈𝐄𝐌
@CarpeDiemUnion · 91 post𝕷𝒊𝗳𝑒 ░⃝ℂ𝚑𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅
@CS_lif · 2231 post𓆩𝕺𝐄𝕷𝖀𝐆𝐄 𝖀𝐍𝐈𝕺𝐍𝐒𓆪
@DELUGE_union · 61 postᰔ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝙃𝟎mℰ
@ELsec_h0m3 · 2431 post『 藤本 』'𝐅𝐋𝐀𝐌𝐈𝐍𝐆/𝐒𝐔𝐍-‘๑’-ᴸᴵᶠᴱ
@FS_CH2 · 1361 post⋅ ⋅ㅤ⎯ ㅤ𝖦𝖠𝖬𝖫𝖤ㅤ⎯ ㅤ 𝘜𝘕𝘐𝘖𝘕 𝘒𝘐𝘕𝘐𝘊𝘏
@GM_K1N1CH · 21 postʜᴀᴠᴇɴ ᴏғ ᴛʜᴇ ᴍᴏᴏɴᶫᶦᶠᵉ
@hvm_life · 4291 post𝐈𝐍𝐅𝐎↭︎𝐋𝐎𝐑✶𝐍𝐓𝟏𝐍𝐄
@L0R4NT1N_info · 1791 post𝑻𝑯𝑬 𝑴𝑶𝑶𝑫𝒀 𝑲𝑵𝒀 ᶫᶦᶠᵉ
@lifethemoodykny · 281 postЗакрыто ⎯꯭۫❨❨̸ 𝗟𝗜𝗙𝕰 𝕮𝗛𝗔𝗡𝗡𝕰𝗟 #𝐖𝕱_𝕻𝐊 ❨❨̸
@Lifewf_pk · 2541 postсоюзы гисиленсы
@meow228CAT6767 · 51 post◌𓈒 ׁ⑅ 𓏪ᣟ݂ ᶫᶦᶠᵉ 𐌑ᥲᧁ𝔦ᥴꪖꪶ 𝔉ᥣꪮᥕꫀ𝔯𝔰 . . .
@MF_l1f · 771 postₘᵢₖᵤ ᵤₙᵢₒₙₛ 𔗂꯭ֺ 𝕮𝐡ɑׁׅ𔓕ִꑄ ִ𝆹𝅥 𓈒𝐒𝕔𝖗ꪱׁׁׁׅׅׅᏢɨ ۫𝆬⃝ ִֺ𝅄𝆹ִֺ𝅥ৎ
@MikunionsCS · 21 post﹫𝗡.𝐀̄𝐑͟𝐀𝑲͟𝐀〞ⁱⁿᶠᵒ
@NARAKAinf · 1701 post𝕷𝐈𝒇𝖤【𝕻𝗮𝘀֟֟፝𝖘꯭𝟏𝕠𝗇】
@pass1onlif · 1551 post𝓘𝓁𝕴𝖓𝖈𝖔𝖌𝖓𝖎𝖙𝖔 𝕽𝖔𝖞𝖆𝖑𝖊. 𝑳𝑰𝑭𝑬
@RI_LFE · 3201 post⾕┃𝗘𝗠𝗘𝗥𝗔𝗟𝗗𝂅ׄ . ۫ 𝗘𝗖𝗟𝗜𝗣𝗦𝗘 ִֺ۪ ִ ⃙𖦹 𝅄
@SB_union · 231 post𝑺𝒕𝒆𝒍𝒍𝒂𝒓 𝒃𝒆𝒈𝒊𝒏𝒏𝒊𝒏𝒈 𝑳𝑰𝑭𝑬
@SBeginningLIFE · 301 post𝑺𝒕𝒆𝒍𝒍𝒂𝒓 𝒃𝒆𝒈𝒊𝒏𝒏𝒊𝒏𝒈 𝑰𝑵𝑭𝑶
@STstellarBeginning · 501 post𝐓𝐁𝐎 𝐮𝐧𝐢𝐨𝐧𝐬
@TBO_unions · 111 post(. 𝗍𝖾𝘁𝗌υ𝗀α𝗄.μㅤㅤ𝗶𝗻𝗳𝗼
@TETSU_info · 3191 post‹‹◞𝐓𝐄𝐓𝐒𝐔⸝⸝𝐆𝐀𝐊𝐔๋࣭ ›› 𝐋𝐈𝐅𝐄
@TETSU_life · 2131 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Adlerman_info named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“𝕴𝐍𝐅𝕺 › 𝐀𝕯𝐋𝕰𝐑𝐌𝕬𝐍” (@Adlerman_info), 228 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Adlerman_info.
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.