Telegram RegisterThe public register of Telegram
Telegram profile photo for NOGA

Channel

NOGA

@yoyo_noga

On this record: Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry

88subscribers

+3 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-1002298289747
TypeChannel
Username@yoyo_noga
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/yoyo_noga

Growth

858886.58 August 2026 — 85 subscribers9 August 2026 — 86 subscribers9 August 2026 — 86 subscribers9 September 2026 — 88 subscribers8 August 20269 September 2026
4 measurements spanning 32 days, net +3. 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 85–88 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 19:0288+2
9 Aug 2026, 16:3186no change
9 Aug 2026, 09:1186+1
8 Aug 2026, 09:0185first reading

Engagement

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

Reaction mix

224 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53842298132527918076428.6%
custom 53865608809829195354721.0%
custom 54000127572086991252310.3%
custom 5386517656432051928229.82%
🕊229.82%
custom 5400022223316618833219.38%
🐳146.25%
custom 5282933396123707680114.91%

Custom emoji. 6 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 14 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 224 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 27 June 2026 to 5 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

5 Aug 2026, 14:02 UTC45 views19 reactionsread 9 August 2026

несмотря на клацклац зубы это всё ещё слоник #digital🟢#sonic

custom 538422981325279180712custom 53865608809829195357

27 Jul 2026, 15:47 UTC77 views1 reactionsread 9 August 2026
Sticker

Sticker, posted without a caption

custom 53842298132527918071

27 Jul 2026, 15:47 UTC71 views20 reactionsread 9 August 2026
Photo

А ЕЩЁ У КЕГИ СЕГОДНЯ ДЕНЬРОЖДЕНИЯ Поздравляйте, я передам

custom 538422981325279180718🕊1custom 54000222233166188331

27 Jul 2026, 15:46 UTC63 views18 reactionsread 9 August 2026
Photo

бебро банда снова на связи‼️🕺 #digital🟢#ББР🟢#кега🟢#мира🟢#карина🟢#палапалас

custom 53865608809829195359custom 54000222233166188336custom 54000127572086991253

22 Jul 2026, 09:23 UTC70 views14 reactionsread 9 August 2026

Во время лета я живу отшельником в лесу. С попугаями. И т.д.

🕊14

22 Jul 2026, 09:22 UTC84 views21 reactionsread 9 August 2026
Photo

чето вокруг себя тоже рисую #traditional

custom 538422981325279180714🕊5custom 53865608809829195352

19 Jul 2026, 07:36 UTC133 views28 reactionsread 9 August 2026
Photo

РЮКУН😆‼️❓‼️❓❓ #digital

🐳14custom 54000127572086991258custom 53865176564320519284custom 53865608809829195352

15 Jul 2026, 09:08 UTC146 views27 reactionsread 9 August 2026
Photo

два брата акробата #traditional🟢#nights

custom 540002222331661883314custom 53865176564320519288custom 52829333961237076803custom 53865608809829195352

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

Named by 1 registered channel — 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.

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

“NOGA” (@yoyo_noga), 88 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/yoyo_noga.

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.