Telegram RegisterThe public register of Telegram
Telegram profile photo for девочка тымэ

Channel

девочка тымэ

@nyangho

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

164subscribers

-4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001535181037
TypeChannel
Username@nyangho
Created28 September 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live5 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/nyangho

Growth

1641681666 August 2026 — 168 subscribers8 August 2026 — 168 subscribers21 August 2026 — 166 subscribers28 August 2026 — 165 subscribers5 September 2026 — 164 subscribers6 August 20265 September 2026
5 measurements spanning 30 days, net -4. 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 163–169 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 22:38164-1
28 Aug 2026, 10:17165-1
21 Aug 2026, 13:27166-2
8 Aug 2026, 15:30168no change
6 Aug 2026, 10:47168first reading

Engagement

13 posts held, back to 20 January 2025the 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 13 posts for this entry, the most recent from 28 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
20s
Average length
10s

Measured directly from 2 videos 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

219 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 79.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 538204748024015290717379.0%
🕊2712.3%
custom 5319232123247271556198.68%

Custom emoji. 2 of the rows above are 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 12 of the 13 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 219 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 20 January 2025 to 28 September 2025, 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

28 Sept 2025, 17:55 UTC179 views21 reactionsread 8 August 2026
Photo

скучаю

custom 538204748024015290713custom 53192321232472715568

5 Aug 2025, 23:14 UTC287 views10 reactionsread 8 August 2026

ладно, я удивлена, что вы переходите в канал

custom 538204748024015290710

5 Aug 2025, 23:02 UTC283 views5 reactionsread 8 August 2026

хорошие времена были в этом канале 😓 кому интересно время от времени меня видеть, ссылка ниже 🤩 https://t.me/darsdard

custom 53820474802401529075

5 Aug 2025, 23:00 UTC254 views3 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 53820474802401529073

15 May 2025, 14:04 UTC311 views31 reactionsread 8 August 2026

в москве 💔🫶

custom 538204748024015290717custom 531923212324727155611🕊3

24 Apr 2025, 15:02 UTC358 views22 reactionsread 8 August 2026

я сняла распаковочку с огромной болталкой о том, где я вообще весь год, чем я сейчас занимаюсь и какие выводы сделаны… ну и стафф супер крутой монтирую?

custom 538204748024015290722

24 Apr 2025, 15:00 UTC340 views18 reactionsread 8 August 2026
Photo

даша paper jungle 🫶🫶🫶🫶

custom 538204748024015290718

3 Apr 2025, 20:33 UTC295 views18 reactionsread 8 August 2026
Photo

меня щас как впервые

custom 538204748024015290718

22 Feb 2025, 22:06 UTC338 views25 reactionsread 8 August 2026

февраль меня встретил новыми траблами со здоровьем, которых я еще и боюсь, но держимся держимся, впереди весна

custom 538204748024015290721🕊4

22 Feb 2025, 22:04 UTC320 views27 reactionsread 8 August 2026
Photo

февральский вкид

custom 538204748024015290727

9 Feb 2025, 15:01 UTC250 views23 reactionsread 8 August 2026
Photo

ого

custom 538204748024015290719🕊4

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“девочка тымэ” (@nyangho), 164 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/nyangho.

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.