- pinned a photo

Channel
ᅠ
@ipendosaah
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
2subscribers
-1 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 | -1002691762782 |
|---|---|
| Type | Channel |
| Username | @ipendosaah |
| Created | 13 May 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 8 October 2026 |
| On Telegram | t.me/ipendosaah |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 26 Sept 2026, 21:42 | 2 | -1 |
| 13 Aug 2026, 17:31 | 3 | no change |
| 7 Aug 2026, 19:13 | 3 | first reading |
Engagement
12 posts held, back to 13 May 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 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 12 posts for this entry, the most recent from 16 June 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
36 reactions across 2 posts, in 8 distinct kinds. The most used accounts for 13.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6167873208025352665 | 5 | 13.9% | |
| custom 6230943952363592422 | 5 | 13.9% | |
| custom 6282910191902004254 | 5 | 13.9% | |
| custom 6309965870231724676 | 5 | 13.9% | |
| custom 6314102202910643707 | 5 | 13.9% | |
| custom 6174848183374449404 | 4 | 11.1% | |
| custom 6320999258963055060 | 4 | 11.1% | |
| custom 6208239471041713023 | 3 | 8.33% |
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 12 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 13 May 2025 to 16 June 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
- pinned a photo
✅موكا لو جيلك بانجت أنجين
Sticker, posted without a caption
ᅠᅠᅠᅠanak presiden 😁
custom 61678732080253526652custom 62309439523635924222custom 62829101919020042542custom 61748481833744494041custom 62082394710417130231custom 63099658702317246761custom 63141022029106437071custom 63209992589630550601
Sticker, posted without a caption
Channel name was changed to «ᅠ»
kalo ngomong tuh jangan tinggi", ntar bacot lu ketabrak helikopter 🫵
Sticker, posted without a caption
bintang nya disini soalnya, sampe dijadiin bahan omongan circle sampah lu. 🌟
custom 63099658702317246764custom 63141022029106437074custom 61678732080253526653custom 61748481833744494043custom 62309439523635924223custom 62829101919020042543custom 63209992589630550603custom 62082394710417130232
Channel photo removed
Channel created
Showing the 12 most recent of 12 posts we hold for @ipendosaah. 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“ᅠ” (@ipendosaah), 2 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/ipendosaah.
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.