Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Fuente Public

Channel

Crypto Fuente Public

@CryptoFuente

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

177subscribers

-5 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-1001194633583
TypeChannel
Username@CryptoFuente
CreatedBetween 1 March 2018 and 25 June 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live1 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/CryptoFuente

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 24 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 why it has no browse page of its own yet.

Growth

177182179.57 August 2026 — 182 subscribers7 August 2026 — 182 subscribers20 August 2026 — 180 subscribers11 September 2026 — 179 subscribers1 October 2026 — 177 subscribers7 August 20261 October 2026
5 measurements spanning 55 days, net -5. 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 176–183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 11:41177-2
11 Sept 2026, 19:41179-1
20 Aug 2026, 18:14180-2
7 Aug 2026, 08:03182no change
7 Aug 2026, 01:18182first reading

Engagement

20 posts held, back to 25 June 2021 — 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 20 posts for this entry, the most recent from 11 March 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

11 Mar 2023, 15:07 UTCviews —

The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.

7 Oct 2022, 07:26 UTC≈1,180 viewsread 7 August 2026

- sponsored message - Hey guys, I'm in a voting contest with my company. Could you quickly vote for Intergiro on this link? It only takes a few seconds. If you send a screenshot to [email protected], I have 3 pairs of Airpods pro to distribute. https://theeuropas.survey.fm/the-europas-awards-2022-public-vote?p=9

23 Jul 2022, 13:03 UTC≈1,380 viewsread 7 August 2026

Binance Futures #1INCH/USDT All take-profit targets achieved 😎 Profit: 88.5322% 📈 Period: 3 Days 13 Hours 34 Minutes ⏰

21 Oct 2021, 02:11 UTC≈2,260 viewsread 7 August 2026

Binance Futures #1INCH/USDT All take-profit targets achieved 😎 Profit: 88.5322% 📈 Period: 3 Days 13 Hours 34 Minutes ⏰

21 Oct 2021, 00:16 UTC≈1,980 viewsread 7 August 2026

Binance Futures #1INCH/USDT Take-Profit target 4 ✅ Profit: 72.0772% 📈 Period: 3 Days 11 Hours 39 Minutes ⏰

20 Oct 2021, 16:23 UTC≈1,800 viewsread 7 August 2026

Binance Futures #1INCH/USDT Take-Profit target 3 ✅ Profit: 56.7598% 📈 Period: 3 Days 3 Hours 46 Minutes ⏰

19 Oct 2021, 21:19 UTC≈1,560 viewsread 7 August 2026

Binance Futures #1INCH/USDT Take-Profit target 2 ✅ Profit: 40.6298% 📈 Period: 2 Days 8 Hours 43 Minutes ⏰

17 Oct 2021, 20:02 UTC≈1,280 viewsread 7 August 2026

Binance Futures #1INCH/USDT Take-Profit target 1 ✅ Profit: 29.2941% 📈 Period: 7 Hours 25 Minutes ⏰

17 Oct 2021, 12:36 UTC≈1,200 viewsread 7 August 2026

⚡️⚡️ #1INCH/USDT ⚡️⚡️ Client: Binance Futures Trade Type: Regular (LONG) Leverage: Isolated (4.0X) Entry Zone: 3.245 - 3.300 Take-Profit Targets: 1) 3.522 - 20% 2) 3.708 - 20% 3) 4.012 - 20% 4) 4.250- 20% 5) 4.548 - 20% Stop Targets: 1) 2.98 - 100.0%

1 Jul 2021, 19:36 UTC≈1,860 viewsread 7 August 2026

Binance Futures #BTC/USDT All take-profit targets achieved 😎 Profit: 33.2851% 📈 Period: 1 Days 4 Hours 24 Minutes ⏰

1 Jul 2021, 10:24 UTC≈1,660 viewsread 7 August 2026

Binance Futures #BTC/USDT Take-Profit target 4 ✅ Profit: 28.9436% 📈 Period: 19 Hours 13 Minutes ⏰

1 Jul 2021, 07:11 UTC≈1,590 viewsread 7 August 2026

Binance Futures #BTC/USDT Take-Profit target 3 ✅ Profit: 24.602% 📈 Period: 16 Hours 0 Minutes ⏰

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

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

“Crypto Fuente Public” (@CryptoFuente), 177 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/CryptoFuente.

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.