Telegram RegisterThe public register of Telegram
Telegram profile photo for $YUNA - Community Group

Supergroup

$YUNA - Community Group

@yunacoin

On this record: Topic · Growth · Engagement · Citations · Cite this entry

101members

-9 since we began measuring on 13 August 2026

2 online right now

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

Register entry

Telegram ID-1002158302425
TypeSupergroup
Username@yunacoin
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 October 2026
Last confirmed live4 November 2026
Measurements held8
Confirmed unchanged3 times, most recently 4 November 2026
On Telegramt.me/yunacoin

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 19 October 2026 and assigned it the closest of 31 fixed categories, at 65% 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 the other topics.

Growth

101110105.513 August 2026 — 110 members23 August 2026 — 108 members29 August 2026 — 107 members5 September 2026 — 105 members13 September 2026 — 106 members25 September 2026 — 103 members19 October 2026 — 103 members20 October 2026 — 101 members13 August 202620 October 2026
8 measurements spanning 68 days, net -9. 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 100–111 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
20 Oct 2026, 23:27101-2
19 Oct 2026, 03:47103no change
25 Sept 2026, 08:58103-3
13 Sept 2026, 05:39106+1
5 Sept 2026, 23:58105-2
29 Aug 2026, 10:36107-1
23 Aug 2026, 05:24108-2
13 Aug 2026, 16:48110first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“$YUNA - Community Group” (@yunacoin), 101 members as measured 20 October 2026. Telegram Register, tgregister.com/channel/yunacoin.

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.