Telegram RegisterThe public register of Telegram
Telegram profile photo for Tapswap Stream Code

Channel

Tapswap Stream Code

@Tapswapstreamcodelive

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

4subscribers

+0 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-1002249951156
TypeChannel
Username@Tapswapstreamcodelive
DescriptionTapswap Stream Code
CreatedBetween 1 July 2024 and 6 July 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live10 October 2026
Measurements held2
On Telegramt.me/Tapswapstreamcodelive

Growth

47 August 2026 — 4 subscribers13 August 2026 — 4 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:174no change
7 Aug 2026, 12:594first reading

Engagement

19 posts held, back to 6 July 2024 — 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 19 posts for this entry, the most recent from 28 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
13
Links
15

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

19 Jul 2024, 02:39 UTC17 viewsread 13 August 2026
Forwarded from @earningfoxePhoto

New Sing-up And Withdraw Bot Link - https://telegram.dog/Dailyprofit01_bot?start=MTUwNjkzNjgzOA== 3 channel join kro bss insta follow krne ki jarurat nahi 5rs bouns milega Upi mai withdraw krlo Per Reffer = Upto 30Rs Hai

17 Jul 2024, 03:04 UTC14 viewsread 13 August 2026
Photo

😃 Fully New USDT Mining Telegram Bot !! 🔥 Daily Free Earning 0.2$ ((₹17)) Per Refer - High Commission Mini Withdrawal 0.5$ ((₹48)) Link - http://t.me/taptether_bot?start=6KHBZQW 3 Day's Mining Karke Withdrawal karlo..!! Join the channel for more bot : join

16 Jul 2024, 04:29 UTC153 viewsread 13 August 2026

🔃All Tapswap codes ✅ Video title: Crypto scandals and triumps Code: 739002 Video title: Tapswap news: highlights from the AMA session on TON's space Code: 5 Video title: Why did Tapswap change the blockchain? Code: 548719 Video title: Why crypto games keep you hooked No code Video title: Tapswap Education:Bitcoin and altcoin Code: 030072 Video title: New in the crypto world Code: 739551 Video title: 5 main cry…

12 Jul 2024, 06:23 UTC16 viewsread 13 August 2026
Photo

Pre- Market Price of $DOGS Average Airdrop 4000x0.042 = $168 Completely FREE ❤️ Don't Miss This Chance Join : https://t.me/dogshouse_bot/join?startapp=J-BUmbMBTGmL9tPOjEOB4A Just Join & Claim ✅ Will Update For Withdrawal & Sell ✅

12 Jul 2024, 01:38 UTC15 viewsread 13 August 2026
Photo

🔄 Notcoin 2.0 Notcoin has been updated, let's check out the changes 👇 Now available: — Leveling up — Withdrawals — Inviting new friends ➡️ Start if you haven't started yet: https://t.me/notcoin_bot?start=er_18108567 Now, those who missed the first phase can participate in Notcoin 2.0 and farm $NOT by completing tasks. 📈 It's great that $NOT is already trading on exchanges, so there's no need to wait for a mythic…

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

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

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.

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

“Tapswap Stream Code” (@Tapswapstreamcodelive), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Tapswapstreamcodelive.

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.