Telegram RegisterThe public register of Telegram
Telegram profile photo for Market Insider

Channel

Market Insider

@MarketInsiderIG

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

11,723subscribers

+11,367 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004295675954
TypeChannel
Username@MarketInsiderIG
DescriptionIf "view" doesn't work - click the 3 dots and open in browser Be the first to know what moves the market
CreatedBetween 1 June 2026 and 2 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/MarketInsiderIG

Topic

Crypto & trading — 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 11 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 the other topics.

Growth

35612,2076,281.57 August 2026 — 356 subscribers8 August 2026 — 2,308 subscribers11 August 2026 — 4,153 subscribers14 August 2026 — 4,676 subscribers17 August 2026 — 4,756 subscribers20 August 2026 — 4,698 subscribers24 August 2026 — 5,297 subscribers27 August 2026 — 5,601 subscribers30 August 2026 — 6,368 subscribers2 September 2026 — 8,072 subscribers6 September 2026 — 9,349 subscribers10 September 2026 — 10,048 subscribers12 September 2026 — 11,081 subscribers14 September 2026 — 11,294 subscribers16 September 2026 — 11,345 subscribers18 September 2026 — 11,602 subscribers1 October 2026 — 12,207 subscribers6 October 2026 — 12,116 subscribers10 October 2026 — 12,051 subscribers13 October 2026 — 11,976 subscribers15 October 2026 — 11,944 subscribers16 October 2026 — 11,915 subscribers17 October 2026 — 11,902 subscribers18 October 2026 — 11,879 subscribers19 October 2026 — 11,871 subscribers20 October 2026 — 11,869 subscribers21 October 2026 — 11,857 subscribers22 October 2026 — 11,851 subscribers23 October 2026 — 11,836 subscribers25 October 2026 — 11,817 subscribers26 October 2026 — 11,804 subscribers27 October 2026 — 11,782 subscribers28 October 2026 — 11,781 subscribers29 October 2026 — 11,775 subscribers30 October 2026 — 11,781 subscribers1 November 2026 — 11,772 subscribers2 November 2026 — 11,767 subscribers3 November 2026 — 11,761 subscribers4 November 2026 — 11,756 subscribers5 November 2026 — 11,747 subscribers6 November 2026 — 11,723 subscribers11,7237 August 20266 November 2026
41 measurements spanning 92 days, net +11,367. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
6 Nov 2026, 14:2611,723-24
5 Nov 2026, 14:2611,747-9
4 Nov 2026, 12:4911,756-5
3 Nov 2026, 11:3911,761-6
2 Nov 2026, 13:3011,767-5
1 Nov 2026, 10:0911,772-9
30 Oct 2026, 10:4411,781+6
29 Oct 2026, 10:1611,775-6
28 Oct 2026, 10:0711,781-1
27 Oct 2026, 10:3011,782-22
26 Oct 2026, 10:5411,804-13
25 Oct 2026, 13:5411,817-19
23 Oct 2026, 13:4911,836-15
22 Oct 2026, 12:0511,851-6
21 Oct 2026, 05:0811,857-12
20 Oct 2026, 06:2611,869-2
19 Oct 2026, 05:3011,871-8
18 Oct 2026, 03:4711,879-23
17 Oct 2026, 00:1611,902-13
16 Oct 2026, 00:5711,915first reading

Engagement

63 posts held, back to 2 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 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.84%
avg views ÷ 11,723 subscribers
Avg views / post
450
43 posts measured
Reaction rate
2.65%
reactions ÷ views · ER floor
Posts in window
43
of 63 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held63 (2 August 2026 – 6 November 2026)
Views total19,347
Reactions total513
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 19:55 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,410
Links
≈1

Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

568 reactions across 63 posts, in 23 distinct kinds. The most used accounts for 73.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤41973.8%
🔥325.63%
🤣284.93%
👍132.29%
😁111.94%
🤬91.58%
😱71.23%
🤔71.23%
🤮71.23%
👏50.88%
🆒40.704%
😈40.704%
👀30.528%
😢30.528%
🤡30.528%
✍20.352%
🍌20.352%
👎20.352%
😭20.352%
🥰20.352%
3 further kinds30.528%

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

Measured over the 63 most recent posts we hold, published 2 August 2026 to 6 November 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

Telegram’s own ‘edited’ marker: 0 of 43 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 18:22 UTC163 views12 reactionsread 6 November 2026
Photo

JUST IN: INFLUENCER MAURITS EXPLAINS THAT HE GOT INTO $PENGU AT $100K MARKET CAP BECAUSE HE SPOTTED THE MEME EARLY, NOT BECAUSE HE HAD INSIDER INFORMATION “I HAD 3 OR 4% OF $PENGU AT $100K MARKET CAP. IT WENT TO $150M” “PEOPLE THOUGHT I HAD INSIDER INFO, BUT I JUST SAW THE MEME EARLY AND THOUGHT IT WAS GOOD” @MarketInsiderIG

❤7👍4👎1

6 Nov 2026, 16:53 UTC277 views12 reactionsread 6 November 2026
Photo

JUST IN: ANSEM UNDER FIRE AS CRYPTO TWITTER SPECULATES THAT HE’S TAKEN A PUMPFUN DEAL @MarketInsiderIG

❤9👀3

6 Nov 2026, 14:32 UTC372 views15 reactionsread 6 November 2026
Photo

JUST IN: TRADERS ALXCOOKS AND 0XETHAN SAY “IF YOU’RE NOT MAKING $100K - $200K EVERY MONTH YOU’RE POOR” “YO ETHAN… WE NEED TO BE MAKING MORE MONEY” “$200K IS NOTHING BRO” @MarketInsiderIG

❤9🤣5👍1

6 Nov 2026, 05:55 UTC792 views18 reactionsread 6 November 2026
Photo

JUST IN: THE US STOCK MARKET LOST THE ENTIRE CRYPTO MARKET CAP WORTH OF VALUE TODAY TODAY’S STOCK MARKET LOSS: $3T TOTAL CRYPTO MARKET CAP: $2.64T @MarketInsiderIG

❤12😱4👍1🔥1

6 Nov 2026, 05:22 UTC571 views11 reactionsread 6 November 2026
Photo

JUST IN: THE NASDAQ 100 HAS FALLEN 8.59% SINCE CZ RANG THE OPENING BELL @MarketInsiderIG

❤6🤔4👍1

6 Nov 2026, 04:54 UTC370 views10 reactionsread 6 November 2026
Photo

JUST IN: TRADER POINT FARM CAPITAL IS DOWN OVER $862,000 TODAY HE IS DOWN OVER $2.1M ON THE MONTH @MarketInsiderIG

❤7🔥2😱1

6 Nov 2026, 03:52 UTC374 views8 reactionsread 6 November 2026
Photo

JUST IN: JASON CALACANIS SAYS ELON MUSK IS IN AN “UNIMAGINABLE AMOUNT OF DANGER” “THESE PEOPLE ARE DERANGED SOCIOPATHIC LUNATICS” @MarketInsiderIG

❤7👍1

6 Nov 2026, 02:57 UTC346 views9 reactionsread 6 November 2026
Photo

JUST IN: RUMORS ANTHROPIC IS LOWERING THEIR IPO TO $1T IN ORDER TO GET IT DONE @MarketInsiderIG

❤9

5 Nov 2026, 22:05 UTC400 views11 reactionsread 6 November 2026
Photo

JUST IN: THREADGUY HAS JOINED FOMO @MarketInsiderIG

❤8🔥3

5 Nov 2026, 21:28 UTC404 views6 reactionsread 6 November 2026
Photo

JUST IN: JASON CALACANIS SAYS THE END OF TRUMP’S TERM IS GOING TO BE ‘PARDON PALOOZA’ “AUTOPEN ON FIRE” @MarketInsiderIG

❤4😁2

5 Nov 2026, 19:57 UTC380 views10 reactionsread 6 November 2026
Photo

JUST IN: ANSEM SAYS HE DOESN’T THINK BITCOIN HOLDS $75,000 “I’M PRETTY CONFIDENT IN A RANGE LOWS RETEST” “I DON’T THINK $75K HOLDS” @MarketInsiderIG

❤6✍2🤔2

5 Nov 2026, 19:15 UTC387 views8 reactionsread 6 November 2026
Photo

JUST IN: FOMO PERPETUALS TRADING RECORDED A NEW ATH AT $414.9M IN VOLUME YESTERDAY PERPS TRADING ACCOUNTED FOR 43% OF YESTERDAY’S REVENUE @MarketInsiderIG

❤6👍2

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

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 30 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Market Insider” (@MarketInsiderIG), 11,723 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/MarketInsiderIG.

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.