Telegram RegisterThe public register of Telegram
Telegram profile photo for TimeFlies Degeneracy Journal

Channel

TimeFlies Degeneracy Journal

@TimeFliesCalls

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

19,571subscribers

+10,021 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-1001739434475
TypeChannel
Username@TimeFliesCalls
DescriptionSharing Alpha Gemz Do your own research. Nothing sent in here is financial advice
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held38
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/TimeFliesCalls

Topic

Other / unclassifiable — 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 57% 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 1 other registered channel. 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
@gregdegens/2065614 Aug 2026, 12:50 UTC@TimeFliesCalls/6980 · this entry14 Aug 2026, 12:50 UTC1.00under a minute
@gregdegens/2069416 Aug 2026, 13:14 UTC@TimeFliesCalls/7039 · this entry16 Aug 2026, 13:14 UTC1.00under a minute
@gregdegens/2070317 Aug 2026, 11:17 UTC@TimeFliesCalls/7044 · this entry17 Aug 2026, 11:17 UTC1.00under a minute
@TimeFliesCalls/7052 · this entry17 Aug 2026, 20:45 UTC@gregdegens/2070917 Aug 2026, 20:45 UTC1.00under a minute
@gregdegens/2071117 Aug 2026, 20:52 UTC@TimeFliesCalls/7055 · this entry17 Aug 2026, 20:52 UTC1.00under a minute
@gregdegens/2071918 Aug 2026, 09:44 UTC@TimeFliesCalls/7068 · this entry18 Aug 2026, 09:44 UTC1.00under a minute
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
@gregdegens6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (5–1)

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. 1 of the 1 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 69 comparable posts for this entry, running 31 July 2026 to 8 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).

Recorded under the key clone_source, 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.

Growth

9,15519,65714,4067 August 2026 — 9,550 subscribers7 August 2026 — 9,550 subscribers7 August 2026 — 9,544 subscribers10 August 2026 — 9,490 subscribers12 August 2026 — 9,473 subscribers16 August 2026 — 9,461 subscribers19 August 2026 — 9,438 subscribers22 August 2026 — 9,408 subscribers25 August 2026 — 9,409 subscribers28 August 2026 — 9,372 subscribers31 August 2026 — 9,358 subscribers3 September 2026 — 9,326 subscribers8 September 2026 — 9,294 subscribers12 September 2026 — 9,251 subscribers17 September 2026 — 9,225 subscribers2 October 2026 — 9,199 subscribers8 October 2026 — 9,176 subscribers14 October 2026 — 9,155 subscribers17 October 2026 — 19,657 subscribers18 October 2026 — 19,651 subscribers20 October 2026 — 19,644 subscribers22 October 2026 — 19,642 subscribers23 October 2026 — 19,635 subscribers24 October 2026 — 19,634 subscribers25 October 2026 — 19,630 subscribers26 October 2026 — 19,626 subscribers27 October 2026 — 19,621 subscribers28 October 2026 — 19,615 subscribers29 October 2026 — 19,611 subscribers31 October 2026 — 19,608 subscribers1 November 2026 — 19,600 subscribers2 November 2026 — 19,599 subscribers2 November 2026 — 19,594 subscribers4 November 2026 — 19,591 subscribers6 November 2026 — 19,586 subscribers7 November 2026 — 19,583 subscribers8 November 2026 — 19,575 subscribers11 November 2026 — 19,571 subscribers19,5717 August 202611 November 2026
38 measurements spanning 96 days, net +10,021. 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 7,580–21,232 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 38
Measured (UTC)SubscribersChange
11 Nov 2026, 00:5419,571-4
8 Nov 2026, 00:1519,575-8
7 Nov 2026, 01:1619,583-3
6 Nov 2026, 00:3719,586-5
4 Nov 2026, 01:2919,591-3
2 Nov 2026, 22:1719,594-5
2 Nov 2026, 00:3819,599-1
1 Nov 2026, 01:5819,600-8
31 Oct 2026, 01:4919,608-3
29 Oct 2026, 23:2619,611-4
28 Oct 2026, 21:4619,615-6
27 Oct 2026, 22:3119,621-5
26 Oct 2026, 19:4019,626-4
25 Oct 2026, 16:1719,630-4
24 Oct 2026, 13:5419,634-1
23 Oct 2026, 11:3019,635-7
22 Oct 2026, 14:3519,642-2
20 Oct 2026, 00:3519,644-7
18 Oct 2026, 22:1819,651-6
17 Oct 2026, 01:3619,657first reading

Engagement

202 posts held, back to 31 July 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.82%
avg views ÷ 19,571 subscribers
Avg views / post
747
34 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
34
of 202 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 8 November 2026
Posts held202 (31 July 2026 – 8 November 2026)
Views total25,403
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 16:16 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,320
Videos
≈126
Links
≈1,700

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

Video runtime
6s
Average length
6s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 34 posts held from the last 30 days (2.94%) 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).

8 Nov 2026, 10:52 UTC746 viewsread 12 November 2026

Let's get some things clear: Sometimes looking at a beautiful chart structure with enticing pattern doesn't mean it will play rightly. Confidently, the team behind a particular project gives signals good play alongside with the chart. That's why in here we do insight research and connect with the project team before making publication.

8 Nov 2026, 09:46 UTC751 viewsread 12 November 2026
Photo

$EXFIL 6FhVPctYg363pQbs4iSvqyHe2cJzfsvFD96gePy6pump

8 Nov 2026, 08:44 UTC746 viewsread 12 November 2026
Photo

$FIBO 0x000DE658153f47f23e92973C8EB1e89762703676 Still appreciating and breaking more barriers. More more more PROFIT!

7 Nov 2026, 17:39 UTC749 viewsread 12 November 2026
Video

Achievement Unlocked: Back with a bang! 💥 After a few days of no calls, @TimeFliesCalls made a x2+ call on fun. $123K ➡️ $246K 👁 View Call 📊 View Stats 🟣 ZELDA - TRENDING #2

6 Nov 2026, 08:04 UTC755 viewsread 12 November 2026
Photo

$WOJAK 8J69rbLTzWWgUJziFY8jeu5tDwEPBwUz4pKBMr5rpump Simplified

4 Nov 2026, 13:11 UTC753 viewsread 12 November 2026
Video

Achievement Unlocked: x3! ☝️ @TimeFliesCalls made a x3+ call on AGENT CITY. $116K ➡️ $360K 👁 View Call 📊 View Stats 🟣 CHOO - TRENDING #2

4 Nov 2026, 13:11 UTC752 viewsread 12 November 2026
Video

Achievement Unlocked: Crosschain King! 🔗👑 @TimeFliesCalls has called a x2+ on 3 different chains recently 👁 View Call 1 👁 View Call 2 👁 View Call 3 📊 View Stats 😎 NEW: SpyDefi LIVE - FREE real-time feed of call alerts

4 Nov 2026, 13:11 UTC751 viewsread 12 November 2026
Video

Achievement Unlocked: Slow Cook! 👨‍🍳 AGENT CITY called by @TimeFliesCalls a few weeks ago just went x2. $116K ➡️ $243K 👁 View Call 📊 View Stats 🪶 LOBIN - TRENDING #2

3 Nov 2026, 07:39 UTC749 viewsread 12 November 2026
Video

Achievement Unlocked: x80! ☄️ @TimeFliesCalls made a x80+ call on 币安人. $42K ➡️ $3.6M 👁 View Call 📊 View Stats 😎 NEW: SpyDefi LIVE - FREE real-time feed of call alerts

3 Nov 2026, 07:39 UTC733 viewsread 12 November 2026
Video

Achievement Unlocked: x70! ☄️ @TimeFliesCalls made a x70+ call on 币安人. $42K ➡️ $3M 👁 View Call 📊 View Stats 🟣 Anakin - TRENDING #2

3 Nov 2026, 07:39 UTC744 viewsread 12 November 2026
Video

Achievement Unlocked: x60! ☄️ @TimeFliesCalls made a x60+ call on 币安人. $42K ➡️ $2.5M 👁 View Call 📊 View Stats 😎 NEW: SpyDefi LIVE - FREE real-time feed of call alerts

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

Posts recorded as deleted after publishing

We recorded 7 posts on @TimeFliesCalls as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
20 August 2026
Most recent seen missing
27 August 2026
Median time before seen missing
20 hours
Seen missing in the last 30 days
0

Forward network

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

Named by 3 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.

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.

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.

☎️中国宝石-匚卄丨几乇丂乇🐳
@cryptogems55552 · 145,834
Telegram ranks this channel #1 of 93 here — alongside 92 others — read 14 August 2026
中国密码鲸公司 🇨🇳🐳🚀🌖
@ChinapumpWXC · 109,052
Telegram ranks this channel #3 of 90 here — alongside 89 others — read 14 August 2026
中國東部加密聯盟 EASTERN CHINA CRYPTO ALLIANCE
@CHINAGEMOFCCCN · 94,569
Telegram ranks this channel #4 of 92 here — alongside 91 others — read 18 August 2026
🐳CODY WHALES CALL 中國🐳
@CODYWHALESCALLS · 215,210
Telegram ranks this channel #8 of 91 here — alongside 90 others — read 11 August 2026
看涨中國人 🇨🇳 DRAGON CALL ☏
@Chinese_dragon_calls · 96,561
Telegram ranks this channel #11 of 90 here — alongside 89 others — read 24 August 2026
Topresale 💎
@topresale · 88,316
Telegram ranks this channel #16 of 85 here — alongside 84 others — read 18 August 2026
Shakers Calls
@marine_CryptoCalls · 70,818
Telegram ranks this channel #45 of 91 here — alongside 90 others — read 20 August 2026
𝐙𝐄𝐔𝐒 𝐆𝐄𝐌 💎
@zeus_gem · 69,337
Telegram ranks this channel #51 of 81 here — alongside 80 others — read 21 August 2026
MiniDraft Calls
@minidraftcalls · 71,033
Telegram ranks this channel #61 of 93 here — alongside 92 others — read 20 August 2026
Sitnikova_travel
@sitnikova_travel · 232,514
Telegram ranks this channel #67 of 78 here — alongside 77 others — read 11 August 2026
Airdrop Comic
@airdropcomic · 336,897
Telegram ranks this channel #75 of 91 here — alongside 90 others — read 10 August 2026
Crypto King Call
@Crypto_KingCall · 150,286
Telegram ranks this channel #83 of 91 here — alongside 90 others — read 15 August 2026

This channel appears in 12 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.

“TimeFlies Degeneracy Journal” (@TimeFliesCalls), 19,571 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/TimeFliesCalls.

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.