Telegram RegisterThe public register of Telegram
Telegram profile photo for loniss_gifts

Channel

loniss_gifts

@lonis_gifts

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

185subscribers

-11 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-1002509543448
TypeChannel
Username@lonis_gifts
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/lonis_gifts

Growth

185196190.57 August 2026 — 196 subscribers8 August 2026 — 196 subscribers16 August 2026 — 194 subscribers23 August 2026 — 191 subscribers31 August 2026 — 187 subscribers9 September 2026 — 186 subscribers18 September 2026 — 185 subscribers7 August 202618 September 2026
7 measurements spanning 42 days, net -11. 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 183–198 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 17:21185-1
9 Sept 2026, 08:15186-1
31 Aug 2026, 10:13187-4
23 Aug 2026, 21:17191-3
16 Aug 2026, 20:38194-2
8 Aug 2026, 11:45196no change
7 Aug 2026, 16:12196first reading

Engagement

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

Reaction mix

111 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 40.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52558508742483991644540.5%
2219.8%
109.01%
❤‍🔥109.01%
👍87.21%
🔥54.50%
🤝54.50%
😁21.80%
🤩21.80%
🎄10.901%
😭10.901%

Custom emoji. One 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 count beside it is 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 15 of the 20 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 24 September 2025 to 29 December 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

29 Dec 2025, 18:15 UTC64 views1 reactionsread 8 August 2026

Бесплатная Лудка на мишку 🧸 Условия: выбить 2 раза 7️⃣7️⃣7️⃣ Крутить в комментариях под постом! Без подписки на канал и чата не выдам! Чат: https://t.me/lonisschat Прокруты бесплатные! Всем удачи 🍀 Завершено, приз выдан(пруфы в комментариях)

1

29 Dec 2025, 17:11 UTC71 views4 reactionsread 8 August 2026

Приветствую всех подписчиков ❤️ Спустя долгое время отсутствия, я начинаю снова вести канал✅ Владелец канала: @loniss_az Я продаю звёзды⭐️по курсу 1.2₽ Телеграм premium ⭐ Через фрагмент 🏴‍☠️ Принимаю оплату:☺️☺️☺️ Чат канала: https://t.me/lonisschat Канал с отзывами: https://t.me/lonissrep Вступайте в чат,буду проводить много раздач 🐶 Давайте проявим активность на этом посте, и я запущу розыгрыш🍀

🔥3🎄1

1 Oct 2025, 20:00 UTC459 views2 reactionsread 8 August 2026

Ночная лудка на 50⭐️ Выбить 1 раз 7️⃣7️⃣7️⃣ Прокрут 1⭐️ Всем удачи 👋 Завершено!

2

1 Oct 2025, 18:39 UTC366 views1 reactionsread 8 August 2026

Результаты конкурса: Победитель: 1. … (@Dreammkks) Проверить результаты

😭1

30 Sept 2025, 11:00 UTC401 views14 reactionsread 8 August 2026

Конкурс на 25⭐️ Итоги на 25 участников🎁 Всем удачи👋

custom 525585087424839916411❤‍🔥2🔥1

29 Sept 2025, 05:19 UTC254 views26 reactionsread 8 August 2026

15 реакций и конкурс

12👍7🤝5custom 52558508742483991642

29 Sept 2025, 04:07 UTC227 viewsread 8 August 2026

Результаты конкурса: Победитель: 1. Makar (@Figneat) Проверить результаты

28 Sept 2025, 16:34 UTC162 views5 reactionsread 8 August 2026

Конкурс на мишку🧸 Итоги на 15 участников Всем удачи🎁

custom 52558508742483991645

28 Sept 2025, 16:33 UTC159 views1 reactionsread 8 August 2026

Кто продаёт нфт, напишите @Loniss_az (покупаю) Кому нужны звёзды тоже пишите (продаю)

👍1

28 Sept 2025, 12:31 UTC203 views8 reactionsread 8 August 2026

Щас будет крупный конкурс

custom 525585087424839916442😁2

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

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.

“loniss_gifts” (@lonis_gifts), 185 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lonis_gifts.

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.