Telegram RegisterThe public register of Telegram
Telegram profile photo for LEADGID Global

Channel

LEADGID Global

@leadgid_global

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

187subscribers

+46 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-1003420030324
TypeChannel
Username@leadgid_global
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/leadgid_global

Topic

Marketing & affiliate — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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

1411871647 August 2026 — 141 subscribers8 August 2026 — 141 subscribers14 August 2026 — 143 subscribers22 August 2026 — 153 subscribers7 September 2026 — 161 subscribers14 September 2026 — 174 subscribers28 September 2026 — 183 subscribers9 October 2026 — 187 subscribers7 August 20269 October 2026
8 measurements spanning 63 days, net +46. 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 134–194 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 12:39187+4
28 Sept 2026, 13:00183+9
14 Sept 2026, 19:42174+13
7 Sept 2026, 05:18161+8
22 Aug 2026, 23:06153+10
14 Aug 2026, 23:43143+2
8 Aug 2026, 22:16141no change
7 Aug 2026, 21:49141first reading

Engagement

10 posts held, back to 5 August 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

135 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 23.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3123.0%
🔥2115.6%
custom 53147427227818068832014.8%
custom 53146679602860849381712.6%
custom 52829908241314067051511.1%
custom 531687860142817351775.19%
🤣75.19%
👍64.44%
😁64.44%
custom 531650311820728803953.70%

Custom emoji. 5 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 7 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 135 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 5 August 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 10 we hold a reading for · 10%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @leadgid_global. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 10 most recent posts we hold for this entry, published 5 August 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 12:42 UTC25 views20 reactionsread 8 August 2026
Photo

If this isn’t in the original cut, we’re gonna be disappointed 🫢

🤣7😁6❤4custom 53146679602860849383

6 Aug 2026, 20:49 UTC44 viewsread 8 August 2026
Photo

Temporary suspension of the offer. Revolut MX CPA ID: 7341

6 Aug 2026, 20:38 UTC55 viewsread 8 August 2026
Photo

Temporary suspension of the offer. Plamigo MX CPS ID: 7367 Plamigo MX [API] CPS ID: 7400

6 Aug 2026, 18:31 UTC53 views5 reactionsread 8 August 2026
Photo

VasXlana MX CPL ID: 7384 From August 7, the payment model for the offer with an application for issuance is changing! Payment for the application - 0 USD (was 1.2 USD) Payment for issuance - 28.80 USD The advertiser also reports that applications are accepted for ages 25 to 65. Please update the information.

custom 53165031182072880395

6 Aug 2026, 13:25 UTC39 views21 reactionsread 8 August 2026
Photo

"Getting clicks but no conversions" — sound familiar? 😨 Our new FAQ guide on financial traffic covers the real problems beginners run into: 🔹 Clicks but zero conversions — check 3 things: page speed, ad/lander match, pixel tracking 🔹 Getting leads but earnings are lower than expected — usually a lead quality issue, not volume 🔹 What a pre-lander is and why it converts better than sending traffic straight to a form …

custom 52829908241314067057custom 53146679602860849387custom 53147427227818068837

6 Aug 2026, 13:22 UTC35 views20 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥7custom 53147427227818068837❤6

5 Aug 2026, 14:02 UTC37 views19 reactionsread 8 August 2026
Photo

🔥 THIS WEEK’S TOP OFFERS ARE HERE A new week means fresh numbers and new leaders. In the slides, you’ll find the offers currently standing out and worth adding to your next test. Take a look, pick your favorites, and see how they perform with your traffic. Your next winning setup might be right here 👀 —————————— Follow us here: 👌 Blog 😀 IG 😀 IN 🌐FB

🔥7❤6👍6

5 Aug 2026, 13:05 UTC40 views25 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤7custom 53146679602860849387custom 53168786014281735177custom 52829908241314067054

5 Aug 2026, 13:04 UTC42 views25 reactions1 Starread 8 August 2026
Video message

Video message, posted without a caption

❤8🔥7custom 53147427227818068836custom 52829908241314067054

5 Aug 2026, 12:00 UTC43 viewsread 8 August 2026
Photo

SakuWang MY CPS ID: 7277 Reduction of payment for the offer: CPS (issued loan) — 9.6 USD (previously 12 USD)

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“LEADGID Global” (@leadgid_global), 187 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/leadgid_global.

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.