Telegram RegisterThe public register of Telegram

Channel

شرح بوت حجز التمويلات •

@YYYYVQ

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1,717subscribers

-4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001915877168
TypeChannel
Username@YYYYVQ
Created11 March 2023measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/YYYYVQ

Growth

1,7171,7211,7196 August 2026 — 1,721 subscribers7 August 2026 — 1,718 subscribers11 August 2026 — 1,717 subscribers6 August 202611 August 2026
3 measurements spanning 4 days, net -4. 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,716–1,722 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 03:051,717-1
7 Aug 2026, 16:531,718-3
6 Aug 2026, 17:161,721first reading

Engagement

7 posts held, back to 11 March 2023the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pagesof 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 7 posts for this entry, the most recent from 12 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 26s
Average length
3m 26s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

12 Jun 2025, 11:56 UTC≈19,100 viewsread 7 August 2026
Voice message

شرح سريع عن طريقة الحجز 3 خطوات بس - @nnvbot

31 May 2025, 18:02 UTC≈19,800 viewsread 7 August 2026
Photo

⏺ بعد ارسال رابط كروبك أو قناتك يطلب منك ارسال الرد الاول والرد الثاني والي يقصد بي الكليشة الي تنزل تحت رابط الكروب اثناء التمويل في حال ماعندك ردود هاي القناة بيهة ردود جاهزه @RTTQO ✈️ الردود المسيئة يتم رفضها وحذف التمويل

31 May 2025, 17:59 UTC≈15,500 viewsread 7 August 2026
Photo

⏺بعد اختيار الوقت ترسل رابط كروبك أو رابط قناتك ومن ثم الردود

31 May 2025, 17:57 UTC≈12,400 viewsread 7 August 2026
Photo

⏺طريقة الحجز داخل البوت - تضغط حجز جديد وتختار الوقت الي يناسبك

31 May 2025, 17:55 UTC≈12,600 viewsread 7 August 2026
Photo

⏺طريقة شحن أو تعبئة بوت النشر عن طريق كارت الاسيا 1-تضغط اضافة رصيد 2- تختار تعبئة كارت او تحويل 3- تكتب رقم الكارت وتدزه

4 Sept 2023, 16:59 UTC≈28,300 viewsread 7 August 2026
Video

- شرح طريقة الشحن عن طريق التحويل والشحن السريع عن طريق الكارت وتثبيت وقت الإعلان .. - بوت الحجز : @nnvbot

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

Citation-graph rank — 710,713 of 1,151,006entries 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.

Mentions

Named by 3 registered channels — 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.

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

“شرح بوت حجز التمويلات •” (@YYYYVQ), 1,717 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/YYYYVQ.

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.