Telegram RegisterThe public register of Telegram
Telegram profile photo for Gini_13 (´ ε ` )♡

Channel

Gini_13 (´ ε ` )♡

@giini_13

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

158subscribers

+7 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-1001959238348
TypeChannel
Username@giini_13
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/giini_13

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

1501581546 August 2026 — 151 subscribers8 August 2026 — 151 subscribers22 August 2026 — 150 subscribers30 August 2026 — 154 subscribers9 September 2026 — 156 subscribers18 September 2026 — 158 subscribers6 August 202618 September 2026
6 measurements spanning 42 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 149–159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 03:21158+2
9 Sept 2026, 14:00156+2
30 Aug 2026, 21:17154+4
22 Aug 2026, 23:27150-1
8 Aug 2026, 19:32151no change
6 Aug 2026, 18:46151first reading

Engagement

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

Reaction mix

83 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 67.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓5667.5%
🍾1315.7%
💋1113.3%
🌚22.41%
💅11.20%

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

Measured over the 10 most recent posts we hold, published 26 May 2026 to 7 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

7 Aug 2026, 13:14 UTC25 views6 reactionsread 8 August 2026
Photo

Теперь есть вот такие стикеры на телефон 💃

🍾6

3 Aug 2026, 19:27 UTC63 views8 reactionsread 8 August 2026
Photo

Хочу брелки со ставкой сделать. Пока что скетчики

🍓8

2 Aug 2026, 07:58 UTC67 views4 reactionsread 8 August 2026
Forwarded from @hppartyPhoto

🥳 Сегодня вас ждём огромное количество постов, а знаете почему? Пора представлять наших замечательных представителей ярмарки и аллеи авторов! Начнем с — GINI13 «Я продаю авторский мерч по популярным и культовым фандомам (Honkai: Star Rail, Dan Da Dan, Wind Breaker, Gintama, Долой безделье), а также линейку оригинальной продукции («Не фандомное»). В ассортименте: принты А5, коллекционные фан- и своп-карты для обмен…

🌚2🍾2

30 Jul 2026, 16:50 UTC79 views7 reactionsread 8 August 2026
Photo

Пока есть силы будут с вами ❤️

🍓6💋1

30 Jul 2026, 07:36 UTC81 views11 reactionsread 8 August 2026
Photo

Ной 💃💃💃❤️❤️❤️❤️

💋10🍓1

23 Jul 2026, 19:16 UTC115 views6 reactionsread 8 August 2026
Photo

Мне так нравится нои, хочу быть как эта женщина

🍾5🍓1

23 Jul 2026, 19:12 UTC91 views8 reactionsread 8 August 2026
Photo

Хочу к 9 августа нарисовать много штук, буду на фесте

🍓8

26 May 2026, 21:50 UTC147 views13 reactionsread 8 August 2026
Photo

я нашла это в галерее, и хочу вам показать

🍓12💅1

Showing the 10 most recent of 10 posts we hold for @giini_13. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Gini_13 (´ ε ` )♡” (@giini_13), 158 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/giini_13.

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.