Telegram RegisterThe public register of Telegram
Telegram profile photo for Market — @Doiro

Channel

Market — @Doiro

@availa

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

57subscribers

-35 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-1001134199894
TypeChannel
Username@availa
CreatedBetween 1 June 2017 and 26 November 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/availa

Growth

579274.57 August 2026 — 92 subscribers9 August 2026 — 92 subscribers16 August 2026 — 74 subscribers23 August 2026 — 57 subscribers7 August 202623 August 2026
4 measurements spanning 15 days, net -35. 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 52–97 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 04:5957-17
16 Aug 2026, 17:1674-18
9 Aug 2026, 13:4792no change
7 Aug 2026, 18:3592first reading

Engagement

19 posts held, back to 26 November 2017the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Jun 2026, 13:32 UTC305 viewsread 9 August 2026
Forwarded from @VouchDoiroPhoto

INSTANT 📱 TikTok Unbans are on FIRE! The best plug for these with 100% success rate on every unban. Message @Doiro with your case!

30 May 2026, 20:09 UTC451 viewsread 9 August 2026

INSTANT 😎 IG UNBANS $890+ | 1hr | 100% Success Rate (Done through a rep, not manual) Send Cases — @Doiro

20 May 2026, 14:07 UTC451 viewsread 9 August 2026

Instant TikTok 📱 No PR Verification $2,000 | 6hrs | 100% Guaranteed Gambling pages are NOT doable. & Must provide proof of ownership + make temporary changes to the account until it’s verified. Send Cases — @Doiro

19 May 2026, 17:55 UTC542 viewsread 9 August 2026

INSTANT 📱 Facebook Ad / BM / Monetization / Payout UNBANS $1,250 Flat | 2hrs | 100% Guaranteed ID + Screenshot Required Send Cases — @Doiro (+ Instant 🤪 Unbans & No PR Verification + Instant 😎 Unbans & Claims active aswell)

11 May 2026, 13:23 UTC475 viewsread 9 August 2026

INSTANT 🤪 TikTok UNBANS $1,990+ | 6hrs | 100% Guaranteed + Shielding included Send Cases — @Doiro

10 Apr 2026, 19:17 UTC756 viewsread 9 August 2026

INSTANT 😎 IG UNBANS Doing these right now! Any page, ban reason. $890 Flat | 1hr | 100% Success Rate Send Cases — @Doiro

2 Mar 2026, 22:42 UTC≈1,190 viewsread 9 August 2026
Photo

INSTANT 😎 IG CLAIMS (TAKEOVERS) 10+ done in the past 24hrs. (2 Today) Last chance to get your desired @ for pennies. Prices will go up by the end of the week! Send Cases — @Doiro ✅

1 Mar 2026, 10:58 UTC≈1,050 viewsread 9 August 2026
Photo

😎 Employee is ONLINE. Send cases — @Doiro ✅

27 Feb 2026, 23:59 UTC≈1,320 viewsread 9 August 2026
Forwarded from @VouchDoiroPhoto

Just completed an INSTANT TikTok 😎 Unban in under 10 MINUTES! Last chance to get your page back, send cases — @Doiro ✈️

21 Feb 2026, 12:29 UTC≈1,030 viewsread 9 August 2026

https://t.me/nft/ScaredCat-15071 BIN — $300 SOLD Message @Doiro to Buy. ✈️

6 Feb 2026, 08:04 UTC≈1,530 viewsread 9 August 2026

https://t.me/nft/ScaredCat-18417 BIN — $1,000 Current Offer — $600 Floor price — 500 TON SOLD Message @Doiro to Offer. ✈️

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Market — @Doiro” (@availa), 57 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/availa.

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.