Telegram RegisterThe public register of Telegram

Channel

Sale

@Limbolato

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

479subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002359995013
TypeChannel
Username@Limbolato
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 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/Limbolato

Growth

4799 Aug 2026, 07:17 — 479 subscribers9 Aug 2026, 19:51 — 479 subscribers9 Aug 2026, 07:179 Aug 2026, 19:51
2 measurements taken within a single day. 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 478–480 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 19:51479no change
9 Aug 2026, 07:17479first reading

Engagement

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

Reaction mix

36 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 36.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1336.1%
🔥616.7%
🥰513.9%
👏411.1%
custom 521339977397700781525.56%
😭25.56%
🤔25.56%
🤯25.56%

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

Measured over the 18 most recent posts we hold, published 29 April 2026 to 25 June 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

25 Jun 2026, 10:55 UTC114 views2 reactionsread 9 August 2026
Forwarded from @Lorre_Insomniac

Тг акк Гардекса взломали ниче там не переходите

2

25 Jun 2026, 04:49 UTC176 views4 reactionsread 9 August 2026
Photo

Стинтлер раздал сваги

🔥31

20 Jun 2026, 15:43 UTC294 views1 reactionsread 9 August 2026

☆ 2 новых юза по YBA: @MrJukesAngels @JackOPlatinum

🔥1

19 Jun 2026, 20:29 UTCviews —

Sale pinned «☆ Напоминание Тгк (500+чел) - 250 ⭐️ Чат (250+ чел) - 250 ⭐️ 😘🥰❤️ Если интересуют юзы то в лс: @Harold_Lorre»

19 Jun 2026, 06:33 UTC279 views1 reactionsread 9 August 2026

✓ Появились новые юзы для продажи! ⭐ Все звезды всегда покупаю в gapcjikstars_bot , там самая низкая цена на них

1

17 Jun 2026, 22:22 UTC286 views1 reactionsread 9 August 2026

♡ Посмотреть все юзы: --- > Здесь < ---

🥰1

12 Jun 2026, 16:45 UTC265 views2 reactionsread 9 August 2026

☆ Напоминание Тгк (500+чел) - 250 ⭐️ Чат (250+ чел) - 250 ⭐️ 😘🥰❤️ Если интересуют юзы то в лс: @Harold_Lorre

1🥰1

11 Jun 2026, 18:29 UTC248 views2 reactionsread 9 August 2026

Кстати все звезды с продажи этого тгк пойдут на дэп в лудку

1🥰1

3 Jun 2026, 19:01 UTC313 views1 reactionsread 9 August 2026
Photo

Всё ещё продаётся Вместе с чатом

🥰1

19 May 2026, 09:37 UTC335 views2 reactionsread 9 August 2026
Forwarded from @Lorre_Insomniac

Кстати юз @LimboLegenda - продаётся. Мой новый юз - @Harold_Lorre

1🥰1

18 May 2026, 21:27 UTC390 views3 reactionsread 9 August 2026

Так и быть отдам за 500 звезд первому кто отпишет

🤯2👏1

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

Citation-graph rank

Citation-graph rank — 346,036 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

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

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

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

“Sale” (@Limbolato), 479 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Limbolato.

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.