Telegram RegisterThe public register of Telegram
Telegram profile photo for Aviator Risk Check

Channel

Aviator Risk Check

@AviatorRiskCheck

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

18,715subscribers

-4,172 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002016767813
TypeChannel
Username@AviatorRiskCheck
Description@AviatorRiskCheck
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live11 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/AviatorRiskCheck

Topic

Gambling & betting — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@AviatorRiskCheck/54413 · this entry3 Nov 2026, 02:40 UTC@avigps/10790910 Nov 2026, 12:17 UTC1.007 days
@AviatorRiskCheck/54689 · this entry4 Nov 2026, 00:51 UTC@avigps/1064724 Nov 2026, 21:47 UTC1.0021 hours
@AviatorRiskCheck/54905 · this entry5 Nov 2026, 00:32 UTC@avigps/1065475 Nov 2026, 08:06 UTC1.007.6 hours
@AviatorRiskCheck/55099 · this entry6 Nov 2026, 02:30 UTC@avigps/1077529 Nov 2026, 23:31 UTC1.004 days
@avigps/1066595 Nov 2026, 20:21 UTC@AviatorRiskCheck/56015 · this entry9 Nov 2026, 12:43 UTC1.004 days
@avigps/1061233 Nov 2026, 10:35 UTC@AviatorRiskCheck/56023 · this entry9 Nov 2026, 14:23 UTC1.006 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@avigps28 (8/8 hand-verifiable sample passed)0.963 days@avigps (15–13)
@rngav25 (8/8 hand-verifiable sample passed)1.005 days@rngav (15–10)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 30 of the 30 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 88 comparable posts for this entry, running 28 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @AviatorRiskCheck — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

18,71522,88720,80112 August 2026 — 22,887 subscribers13 August 2026 — 22,871 subscribers14 August 2026 — 22,789 subscribers16 August 2026 — 22,680 subscribers17 August 2026 — 22,587 subscribers18 August 2026 — 22,517 subscribers19 August 2026 — 22,465 subscribers20 August 2026 — 22,423 subscribers21 August 2026 — 22,343 subscribers23 August 2026 — 22,245 subscribers24 August 2026 — 22,124 subscribers25 August 2026 — 22,021 subscribers26 August 2026 — 21,953 subscribers27 August 2026 — 21,920 subscribers28 August 2026 — 21,871 subscribers29 August 2026 — 21,805 subscribers30 August 2026 — 21,746 subscribers31 August 2026 — 21,681 subscribers1 September 2026 — 21,621 subscribers2 September 2026 — 21,562 subscribers4 September 2026 — 21,498 subscribers7 September 2026 — 21,351 subscribers10 September 2026 — 21,152 subscribers12 September 2026 — 21,059 subscribers14 September 2026 — 20,982 subscribers15 September 2026 — 20,908 subscribers18 September 2026 — 20,818 subscribers30 September 2026 — 20,291 subscribers6 October 2026 — 20,069 subscribers10 October 2026 — 19,921 subscribers13 October 2026 — 19,764 subscribers14 October 2026 — 19,719 subscribers15 October 2026 — 19,668 subscribers16 October 2026 — 19,625 subscribers17 October 2026 — 19,601 subscribers18 October 2026 — 19,565 subscribers19 October 2026 — 19,536 subscribers20 October 2026 — 19,493 subscribers21 October 2026 — 19,437 subscribers22 October 2026 — 19,382 subscribers23 October 2026 — 19,360 subscribers24 October 2026 — 19,309 subscribers25 October 2026 — 19,286 subscribers26 October 2026 — 19,257 subscribers27 October 2026 — 19,210 subscribers28 October 2026 — 19,185 subscribers29 October 2026 — 19,136 subscribers30 October 2026 — 19,096 subscribers31 October 2026 — 19,064 subscribers1 November 2026 — 19,021 subscribers2 November 2026 — 18,996 subscribers3 November 2026 — 18,962 subscribers4 November 2026 — 18,938 subscribers5 November 2026 — 18,900 subscribers6 November 2026 — 18,870 subscribers7 November 2026 — 18,847 subscribers8 November 2026 — 18,807 subscribers9 November 2026 — 18,768 subscribers11 November 2026 — 18,715 subscribers12 August 202611 November 2026
59 measurements spanning 91 days, net -4,172. 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 18,089–23,513 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
11 Nov 2026, 15:1618,715-53
9 Nov 2026, 22:0018,768-39
8 Nov 2026, 16:1618,807-40
7 Nov 2026, 12:4918,847-23
6 Nov 2026, 16:0718,870-30
5 Nov 2026, 13:1818,900-38
4 Nov 2026, 14:1918,938-24
3 Nov 2026, 14:3418,962-34
2 Nov 2026, 16:4618,996-25
1 Nov 2026, 17:4019,021-43
31 Oct 2026, 14:0719,064-32
30 Oct 2026, 15:0919,096-40
29 Oct 2026, 16:5119,136-49
28 Oct 2026, 16:0619,185-25
27 Oct 2026, 18:4719,210-47
26 Oct 2026, 17:0619,257-29
25 Oct 2026, 15:3819,286-23
24 Oct 2026, 17:3619,309-51
23 Oct 2026, 17:5819,360-22
22 Oct 2026, 21:2019,382first reading

Engagement

1,200 posts held, back to 12 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 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.008%
avg views ÷ 18,715 subscribers
Avg views / post
1.5
360 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
360
of 1,200 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 11 November 2026
Posts held1,200 (12 August 2026 – 11 November 2026)
Views total530
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 16:14 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
≈5,350
Links
≈6,170

Lifetime counters from Telegram’s own channel header, read 11 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

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
⚡150.0%
❤150.0%

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

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 August 2026 to 11 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 360 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).

11 Nov 2026, 15:53 UTC2 viewsread 11 November 2026

⭐ 𝗦𝗜𝗚𝗡𝗔𝗟 𝗖𝗔𝗡𝗖𝗘𝗟𝗟𝗘𝗗 ⭐ Status: Reset ⭐ Next signal: Pending

11 Nov 2026, 15:52 UTC2 viewsread 11 November 2026

⭐ 𝗔𝗩𝗜𝗔𝗧𝗢𝗥 𝗔𝗟𝗘𝗥𝗧 ⭐ Signal incoming ⭐ Stay ready

11 Nov 2026, 15:50 UTC2 viewsread 11 November 2026

⭐ 𝗦𝗜𝗚𝗡𝗔𝗟 𝗖𝗔𝗡𝗖𝗘𝗟𝗟𝗘𝗗 ⭐ Status: Reset ⭐ Next signal: Pending

11 Nov 2026, 15:49 UTC2 viewsread 11 November 2026

⭐ 𝗔𝗩𝗜𝗔𝗧𝗢𝗥 𝗔𝗟𝗘𝗥𝗧 ⭐ Signal incoming ⭐ Stay ready

11 Nov 2026, 15:34 UTC2 viewsread 11 November 2026

⭐ 𝗦𝗜𝗚𝗡𝗔𝗟 𝗖𝗔𝗡𝗖𝗘𝗟𝗟𝗘𝗗 ⭐ Status: Reset ⭐ Next signal: Pending

11 Nov 2026, 15:34 UTC2 viewsread 11 November 2026

⭐ 𝗔𝗩𝗜𝗔𝗧𝗢𝗥 𝗔𝗟𝗘𝗥𝗧 ⭐ Signal incoming ⭐ Stay ready

11 Nov 2026, 14:45 UTC2 viewsread 11 November 2026

⭐ 𝗦𝗜𝗚𝗡𝗔𝗟 𝗖𝗔𝗡𝗖𝗘𝗟𝗟𝗘𝗗 ⭐ Status: Reset ⭐ Next signal: Pending

11 Nov 2026, 14:45 UTC2 viewsread 11 November 2026

⭐ 𝗔𝗩𝗜𝗔𝗧𝗢𝗥 𝗔𝗟𝗘𝗥𝗧 ⭐ Signal incoming ⭐ Stay ready

11 Nov 2026, 14:38 UTC1 viewsread 11 November 2026

⭐ 𝗦𝗜𝗚𝗡𝗔𝗟 𝗖𝗔𝗡𝗖𝗘𝗟𝗟𝗘𝗗 ⭐ Status: Reset ⭐ Next signal: Pending

11 Nov 2026, 14:37 UTC1 viewsread 11 November 2026

⭐ 𝗔𝗩𝗜𝗔𝗧𝗢𝗥 𝗔𝗟𝗘𝗥𝗧 ⭐ Signal incoming ⭐ Stay ready

11 Nov 2026, 14:31 UTC1 viewsread 11 November 2026

⭐ 𝗦𝗜𝗚𝗡𝗔𝗟 𝗖𝗔𝗡𝗖𝗘𝗟𝗟𝗘𝗗 ⭐ Status: Reset ⭐ Next signal: Pending

11 Nov 2026, 14:30 UTC1 viewsread 11 November 2026

⭐ 𝗔𝗩𝗜𝗔𝗧𝗢𝗥 𝗔𝗟𝗘𝗥𝗧 ⭐ Signal incoming ⭐ Stay ready

Showing the 12 most recent of 1,200 posts we hold for @AviatorRiskCheck. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Payouts Helper™
@PayoutsHelper · 41,549
Telegram ranks this channel #10 of 47 here — alongside 46 others — read 28 August 2026
CryptoFlash: Breaking news
@Airdropxcaptain · 43,671
Telegram ranks this channel #15 of 54 here — alongside 53 others — read 27 August 2026
We Cog ™
@noqro · 41,209
Telegram ranks this channel #15 of 50 here — alongside 49 others — read 27 August 2026
Yono games
@AirdropEnvoy · 84,552
Telegram ranks this channel #15 of 47 here — alongside 46 others — read 17 August 2026
Airdrop Ambition
@AirdropAmbition · 143,719
Telegram ranks this channel #15 of 49 here — alongside 48 others — read 12 August 2026
PRO LOOTERS
@prolooteresss · 41,069
Telegram ranks this channel #17 of 48 here — alongside 47 others — read 26 August 2026
Devil Earning
@devil_drop · 72,200
Telegram ranks this channel #18 of 46 here — alongside 45 others — read 18 August 2026
Thunders Airdrop
@ThundersAirdrop · 53,012
Telegram ranks this channel #20 of 49 here — alongside 48 others — read 22 August 2026
Earning vip
@EarningEnvy · 50,281
Telegram ranks this channel #21 of 49 here — alongside 48 others — read 24 August 2026
Crypto Blunder
@CryptoBlunder · 53,305
Telegram ranks this channel #21 of 48 here — alongside 47 others — read 22 August 2026
CASINO ALERTS
@AIRDROPS_ALERTERS · 52,674
Telegram ranks this channel #21 of 48 here — alongside 47 others — read 22 August 2026
Thunder drop♠️♦️
@Thunder_drop · 51,983
Telegram ranks this channel #22 of 49 here — alongside 48 others — read 22 August 2026
Fart Airdrop ™
@FartAirdrop · 42,147
Telegram ranks this channel #23 of 48 here — alongside 47 others — read 26 August 2026
Airdrop HiveX™
@AirdropHiveX · 56,149
Telegram ranks this channel #23 of 46 here — alongside 45 others — read 22 August 2026
Blunder Airdrop
@BlunderAirdrop · 40,890
Telegram ranks this channel #25 of 50 here — alongside 49 others — read 27 August 2026
Airdrop Neptune™
@AirdropNeptune · 95,818
Telegram ranks this channel #26 of 49 here — alongside 48 others — read 15 August 2026
METRO REPORT 🗞
@metroreporten · 57,286
Telegram ranks this channel #27 of 48 here — alongside 47 others — read 19 August 2026
Airdrop Segment
@AirdropSegment · 66,556
Telegram ranks this channel #28 of 47 here — alongside 46 others — read 19 August 2026
Airdrop Lite
@airdrops_lite · 54,633
Telegram ranks this channel #31 of 47 here — alongside 46 others — read 22 August 2026
Airdrop Denver
@AirdropDenver · 147,365
Telegram ranks this channel #33 of 47 here — alongside 46 others — read 21 August 2026

This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Aviator Risk Check” (@AviatorRiskCheck), 18,715 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/AviatorRiskCheck.

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.