Telegram RegisterThe public register of Telegram
Telegram profile photo for Fresh Sourcing Data 2026

Channel

Fresh Sourcing Data 2026

@freshsource2026

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

4subscribers

+3 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-1003876822115
TypeChannel
Username@freshsource2026
Created6 May 2026 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live15 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/freshsource2026

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 15 November 2026 and assigned it the closest of 31 fixed categories, at 97% 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

142.57 August 2026 — 1 subscribers15 August 2026 — 1 subscribers15 August 2026 — 2 subscribers15 November 2026 — 4 subscribers7 August 202615 November 2026
4 measurements spanning 100 days, net +3. 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 1–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 22:474+2
15 Aug 2026, 00:562+1
15 Aug 2026, 00:001no change
7 Aug 2026, 19:191first reading

Engagement

3 posts held, back to 6 May 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 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 3 posts for this entry, the most recent from 20 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 May 2026, 16:03 UTC≈1,350 viewsread 15 August 2026

🚨 Exclusive Leads Available – France, Belgium, Spain & Netherlands! 🌍 Gain access to high-quality, verified data with the following details: 📞 Phone Number 🧑‍💼 First & Last Name 🎂 Date of Birth ⚧ Gender 🏡 Full Address 🔓 Breach Alert – Breached in 2026 💳 🔥 Fresh Bank Leads with IBAN & WhatsApp Leads Available! 📲 Cellphone & WhatsApp Leads available for most countries! Common Headers for Bank Leads: 🔹 First Name 🔹 L…

Showing the 3 most recent of 3 posts we hold for @freshsource2026. 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“Fresh Sourcing Data 2026” (@freshsource2026), 4 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/freshsource2026.

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.