Telegram RegisterThe public register of Telegram
Telegram profile photo for 🩵 𝖵ᎥԵɑׁׅmᎥ𐓣ed 𝖮𐓣𝖾ׅ꯱⍴ɑׁׅrӄ

Channel

🩵 𝖵ᎥԵɑׁׅmᎥ𐓣ed 𝖮𐓣𝖾ׅ꯱⍴ɑׁׅrӄ

@onesparrk

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

235subscribers

-7 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-1002771524997
TypeChannel
Username@onesparrk
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/onesparrk

Growth

235246240.58 August 2026 — 242 subscribers8 August 2026 — 242 subscribers8 August 2026 — 241 subscribers16 August 2026 — 242 subscribers22 August 2026 — 246 subscribers30 August 2026 — 241 subscribers8 September 2026 — 243 subscribers16 September 2026 — 235 subscribers8 August 202616 September 2026
8 measurements spanning 39 days, net -7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 233–248 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 00:19235-8
8 Sept 2026, 06:56243+2
30 Aug 2026, 15:37241-5
22 Aug 2026, 22:15246+4
16 Aug 2026, 03:06242+1
8 Aug 2026, 19:28241-1
8 Aug 2026, 09:47242no change
8 Aug 2026, 04:15242first reading

Engagement

18 posts held, back to 2 August 2026the 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 18 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
14s
Average length
14s

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.

Reaction mix

28 reactions across 3 posts, in 8 distinct kinds. The most used accounts for 17.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5296275858057635658517.9%
custom 5305728024514173848517.9%
custom 5303492004410336627414.3%
custom 5307786280216602395414.3%
custom 5296631318140985687310.7%
custom 5305324215983971147310.7%
custom 527625383721517945027.14%
custom 529678021606720346627.14%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 3 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 2 August 2026 to 8 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

8 Aug 2026, 07:04 UTC32 viewsread 8 August 2026

лапы вы не знаете тгк где делают тизеры?? 😊😊

8 Aug 2026, 06:51 UTC28 viewsread 8 August 2026
Forwarded from @milsuto_fldPhoto

❤️‍🔥 _ 𝐌𝗶𝗹𝗌𝗎𝔗𝕠 𝐀𝗋𝖾 𝐋𝕠𝕠𝒌𝗂𝗇’ 𝔉𝒐𝗿 𝑯ью @𝐌ил𝖼𝕪т𝒐 в п𝒐и𝖼𝗸𝕒х Нью 🗯️ Чт𝒐 н𝗒жн𝕠 𝐜д𝒆л𝕒ть чт𝒐бы в𝒄т𝕪пить 𝐁 Н𝒂ш Ч𝕒т? 🍭 규칙 01П𝗉𝒐чит𝕒ть П𝗽𝒂вил𝕒 02 Выб𝗉𝐚ть 𝐏𝒐ль 역할 👍 소유자 03 Н𝐚пи𝗰𝕒ть Вл𝒂д𝖾льц𝕪

8 Aug 2026, 05:35 UTC31 viewsread 8 August 2026
Forwarded from @anlsfldFile

하늘𝓝𝖾𝗐.video & 𝐍𝖾𝗐𝖩𝖾𝖺𝗇𝗌 📞 𝐈 𝐣𝗎𝗌𝗍 𝐰𝖺𝗇𝗍 𝗒𝐨𝗎 𝖼𝖺𝐥𝗅 𝐦𝗒 𝗉𝐡𝗈𝗇𝐞 𝐫𝗂𝗀𝗁𝐭 𝗇𝐨𝗐 🌟id : our edit : kai 🌟

8 Aug 2026, 05:31 UTC23 views3 reactionsread 8 August 2026
Forwarded from @TwoSeidPhoto

ᅠ TWOSEID 🌾 NEW ERA your forest friends __ 🌟🌟 08 :08 🌟 Na Na Na

custom 52962758580576356581custom 53053242159839711471custom 53057280245141738481

7 Aug 2026, 13:18 UTC66 viewsread 8 August 2026

🩷 봉고 𝐎neS𝗉𝖺rk 𝐔pdate 💛 🐻 #𝐎neRp & #𝖮𝗇eRc ! !

Showing the 12 most recent of 18 posts we hold for @onesparrk. 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.

Forward network

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

Named by 5 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.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“🩵 𝖵ᎥԵɑׁׅmᎥ𐓣ed 𝖮𐓣𝖾ׅ꯱⍴ɑׁׅrӄ” (@onesparrk), 235 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/onesparrk.

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.