Channel
@Didyoureallyknow
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
16,731subscribers
-190 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001123420940 |
|---|---|
| Type | Channel |
| Username | @Didyoureallyknow |
| Description | Our Primary focus is to share the unknown facts with you. Hope you like it. ➡️Some time I have to post ads. |
| Created | Between 1 June 2017 and 31 October 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/Didyoureallyknow |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 16:55 | 16,731 | -5 |
| 24 Aug 2026, 17:46 | 16,736 | -11 |
| 23 Aug 2026, 01:46 | 16,747 | -11 |
| 21 Aug 2026, 11:47 | 16,758 | -10 |
| 20 Aug 2026, 08:06 | 16,768 | -7 |
| 19 Aug 2026, 04:47 | 16,775 | -10 |
| 18 Aug 2026, 06:31 | 16,785 | -8 |
| 17 Aug 2026, 10:05 | 16,793 | -20 |
| 15 Aug 2026, 15:56 | 16,813 | -18 |
| 14 Aug 2026, 03:47 | 16,831 | -13 |
| 13 Aug 2026, 00:14 | 16,844 | -15 |
| 11 Aug 2026, 21:16 | 16,859 | -4 |
| 10 Aug 2026, 23:38 | 16,863 | -12 |
| 9 Aug 2026, 21:12 | 16,875 | -13 |
| 8 Aug 2026, 21:37 | 16,888 | -9 |
| 8 Aug 2026, 00:21 | 16,897 | -17 |
| 6 Aug 2026, 23:41 | 16,914 | -7 |
| 6 Aug 2026, 02:18 | 16,921 | first reading |
25 posts held, back to 3 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 39 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 23 August 2026 |
|---|---|
| Posts held | 25 (3 July 2026 – 23 August 2026) |
| Views total | 19,366 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Aug 2026, 00:21 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.
Lifetime counters from Telegram’s own channel header, read 26 August 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.
🚀 VIP ACCESS OPEN I am launching a new VIP access for those who want to improve their knowledge in crypto and trading. What is included in VIP: 🎓 Online training - a structured knowledge base from the basics to practical trading 🤖 Access to a trading bot - a tool for automating trading processes 📊 Market reviews and analytics - analysis of the market situation and key opportunities 🎁 Additional bonuses and materia…
#ETH/USDT ANALYSIS ETH has broken out of the descending triangle pattern with significant volume, triggering a strong rally. Currently, it is retesting the breakout level, with the former supply zone now acting as a key demand area. A successful retest could lead to further upside, while a failed retest may trigger a downward move.
#BTC DOMINANCE ANALYSIS BTC.D is rebounding from the support trendline of the rising wedge pattern and is currently trading above the Ichimoku cloud, which is acting as support. A breakout above the wedge resistance trendline would invalidate the pattern and signal further upside. On the other hand, a breakdown below the wedge support would confirm further downside in BTC Dominance. It’s important to note that BT…
#USDT DOMINANCE ANALYSIS USDT Dominance is trading below the resistance trendline of the symmetrical triangle, indicating continued consolidation. The Ichimoku cloud is acting as support below the current price action. We need to wait for a solid breakout or breakdown to confirm the next directional move. It’s important to note that USDT Dominance often exhibits an inverse correlation with the broader cryptocurre…
#BTC/USDT ANALYSIS Bitcoin has broken out of the descending triangle with strong volume, signaling a bullish shift in momentum. Price is now moving in for a retest of the Ichimoku cloud and the broken trendline. A successful hold above these levels would confirm bullish continuation, watch price action closely.
#BTC/USDT ANALYSIS Bitcoin has broken above the descending triangle resistance trendline, signaling a potential shift in momentum. The 50MA is currently acting as a resistance barrier, limiting further upside. A successful breakout above the 50MA would confirm strength and could trigger a continued upward rally.
#TURBO/USDT ANALYSIS TURBO is consolidating within a falling wedge pattern and is currently holding above the support trendline. This structure suggests a potential bullish setup, where a confirmed breakout could trigger upward momentum. However, a breakdown below the wedge would invalidate the pattern and signal further downside, watch price action closely.
#BTC DOMINANCE ANALYSIS BTC.D is consolidating within a rising wedge while trading inside the Ichimoku cloud, signaling indecision. Price remains in a neutral zone with no clear trend direction.A confirmed breakout or breakdown will determine the next move. It’s important to note that BTC Dominance often shares an inverse relationship with the altcoin market cap.
#BTC/USDT ANALYSIS Bitcoin has broken down from the symmetrical triangle with strong volume, indicating bearish momentum. It is currently holding above a horizontal demand zone, while the Ichimoku cloud acts as resistance overhead. A retest of the triangle is likely, and a breakdown below the demand zone would open the door for further downside. Monitor price action closely for confirmation.
#BTC/USDT ANALYSIS Bitcoin is trading below the Ichimoku cloud, which is acting as a strong resistance following the breakdown from the rising wedge pattern. A breakout above the cloud could trigger a bullish rally, while a breakdown below the 200 MA would likely lead to further market correction.
#BTC/USDT ANALYSIS Bitcoin has broken down from the rising wedge pattern and is trending lower, indicating growing bearish momentum, but it is still holding above the 100 MA, which is acting as a key support level. A bounce from this area could trigger a short-term recovery, while a decisive breakdown below the 100 MA would likely confirm further downside and extend the ongoing market correction.
#USDT DOMINANCE ANALYSIS USDT Dominance is getting rejected from the descending triangle resistance trendline, indicating weakening strength. The Ichimoku cloud is also acting as a strong resistance barrier above the current price action, adding further pressure. At this stage, patience is key a confirmed breakout above the pattern or a breakdown below support will determine the next clear directional move. It’s …
Showing the 12 most recent of 25 posts we hold for @Didyoureallyknow. 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 — 1,541,661 of 1,604,161entries 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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Did You Know” (@Didyoureallyknow), 16,731 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/Didyoureallyknow.
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.