Channel
@BPinff
On this record: Growth · Engagement · Posts · Citations · Cite this entry
18subscribers
+7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004301827619 |
|---|---|
| Type | Channel |
| Username | @BPinff |
| Created | 21 June 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/BPinff |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 07:57 | 18 | +2 |
| 8 Sept 2026, 09:39 | 16 | +2 |
| 22 Aug 2026, 20:28 | 14 | +3 |
| 12 Aug 2026, 07:01 | 11 | no change |
| 6 Aug 2026, 22:42 | 11 | first reading |
5 posts held, back to 21 June 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 5 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
˖ ⸂۪ ፝֠ ꒱𐇽᳟҇۫ ࿔⋅ ⃪ֵ𝆋𝆋𝆋𝆋𝆋𐇽ؖпр⃪ۣ⃔а⃪в⃪ؘؙܹᰰиׅิ⃪ꪒؘؔ፝а⃪ׅ֮ܵۜᩬ в⃪ֵֿ֖𐇽ؖп дֱؙ᷁ؑꪒ⃪ؘؔ፝я к⃪ׅ֮ܵۜᩬᥲ⃪ܹۭ︩︪֟ؕнֱؙ᷁ؑа⃪ۣ⃔݀۬лִ۪ั۫݀۬а ៸៸᳕ ۫۫ ۫᷼ ᩘ⃨◌⃘ֵ۫ ፝֟.·⸼ִ 𓈒ֵ۫ о⃪ؘؙܹᰰбыִ۪ั۫݀۬ч︩︪нֱؙ᷁ؑый в⃪ؘؙܹᰰп◞ ᷒ᰰຼ ׅ .︵ֹ᳕᷼ 🤩порог со схожей тематикой — 450+ пдп 🤩порог с другой тематикой — 700+ пдп . . ( тематики, не относящиеся к символам/оформлению/пакам/баннерам/т.д. ) 🤩повтор вп через 2 дня ︵᳟ۣ︡۫ ۫۫᷼ ֹ ِ𝃡 ՟…
𝆹 .ؑ ིׅ֩ᰰ 𓈒 ︵ ۫᷼ 𝂅 𝐩⃪𐇽፝𝐫𝐢⃪ׅ֩ᰰꠂ𝐜۫۫𝐞⃪𐇽ׅ֩ᰰܵ 𓏻 ۟ . ֹ.᷒ ꤮۪⏜ؖ᷼. н⃪и⃨ؗк — 𝟏𝟓⃪ з︩︪ϐؗ / 𝟐ׄ𝟓 р⃪ؘؙܹᰰ⃪уб⃪ о⃪ؘؙܹᰰпиִ۪ั۫݀۬са⃪ؘؙܹᰰни︩︪ꫀ м⃪ܹۭ︩︪֟ؕак⃪ׅ֮ܵۜᩬс. — 𝟐ׄ𝟓 з⃪ϐ / 𝟓𝟎๋ р⃪ؘؙܹᰰ⃪уб о⃪ؘؙܹᰰпиִ۪ั۫݀сֱؙ᷁ؑа⃪ؘؙܹᰰниؕꫀ ო⃪и⃪нׅิۢ. — 𝟏𝟓⃪ звؘܹ / ⃪𝟐𝟓 р⃪ؘؙܹᰰ⃪уб⃪ п⃪ۣ⃔݀۬есִ۪ั۫݀۬н⵿ؖя — 𝟐ؕ𝟓 з⃪⃜ϐ / 𝟕𝟎๋ рuᩛ⃪б а⃪ֵֿ֖𐇽ؖдрֱؙ᷁ؑесִ۪ั⃪۫݀۬ — 𝟏𝟓⃪ з︩︪ϐؗ / 𝟐ׄ𝟓 р⃪ؘؙܹᰰ⃪уб⃪ ᰰᩙᩖ𑪍 . ྀི࣯࣯𐇽⃨ׅ۫֩ ֖𝆹 𓏻 ‛‛ ۪۪. ︵ؖ᷼᷼ ᡴꪫ⃜ 𝐞⃪𐇽᪶፝…
1 чл. — 1.5 зв, макс 20 чл.🙂 на закрытие неделя, добив тематом, возврат только если не добиваю ссылку .🙂🙂🙂🙂 июль : договор. 🙂🙂🙂 🙂🙂🙂 12ч — 25 зв , 24ч — 50 зв , 1 подгон бесплатно, остальные — 5 зв, закреп — 30зв 🙂🙂 июль : договор. дата 🙂🙂 😀😀🙂🙂🙂🙂🙂🙂🙂🙂 я не отвечаю за отписки !! после рек/привода просьба написать +реп . писать @jap_loga
вп предлагать сюда
Channel created
Showing the 5 most recent of 5 posts we hold for @BPinff. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“𓈒ׅᩬ⃪ۣ⑅⃪ْ࡙۪۟፝͟🄱𐇽ᩙ⃞⃪ᩞ̸🄿ܸິ⃪ུۣؗۗ⃐۟۟ܳ ⃪᳟ۢ۫۫◌⃘⃪ۣ⃨𐨌𑂴𝐈⃪︩︪⃜፝𝐧⃪͝𝐟⃪᷒ᰰຼ𝐨̸𝅦𓂂𐇽᪲𝇄⃪݂” (@BPinff), 18 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/BPinff.
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.