The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 18 days, that account will self-destruct and this channel will no longer have an owner.

Channel
kevoswipes • REVIEWS
@FraudBibleReviews
On this record: Topic · Growth · Engagement · Posts · Cite this entry
87subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001171062149 |
|---|---|
| Type | Channel |
| Username | @FraudBibleReviews |
| Created | Between 1 March 2018 and 6 July 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 3 times, most recently 10 October 2026 |
| On Telegram | t.me/FraudBibleReviews |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 15:39 | 87 | -1 |
| 8 Sept 2026, 02:16 | 88 | -1 |
| 22 Aug 2026, 15:26 | 89 | -4 |
| 14 Aug 2026, 12:28 | 93 | +2 |
| 9 Aug 2026, 14:02 | 91 | no change |
| 6 Aug 2026, 20:23 | 91 | first reading |
Engagement
20 posts held, back to 6 July 2020 — 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 20 posts for this entry, the most recent from 21 March 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
—————————- 🏦 Payment Method 💳 BTC 📅 Date 05/08/2020
—————————- 🏦 Payment Method 💳 BTC 📅 Date 04/08/2020
—————————- 🏦 Payment Method 💳 BTC 📅 Date 24/07/2020
—————————- 🏦 Payment Method 💳 BTC 📅 Date 23/07/2020
—————————- 🏦 Payment Method 💳 BTC 📅 Date 23/07/2020
—————————- 🏦 Payment Method 💳 PayPal 📅 Date 22/07/2020
—————————- 🏦 Payment Method 💳 BTC 📅 Date 21/07/2020
—————————- 🏦 Payment Method 💳 PayPal 📅 Date 20/07/2020
—————————- 🏦 Payment Method 💳 BTC 📅 Date 18/07/2020
—————————- 🏦 Payment Method 💳 PayPal 📅 Date 17/07/2020
—————————- 🏦 Payment Method 💳 PayPal 📅 Date 17/07/2020
Showing the 12 most recent of 20 posts we hold for @FraudBibleReviews. 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 September 2026 — this entry's latest reading, not the date you are reading this.
“kevoswipes • REVIEWS” (@FraudBibleReviews), 87 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/FraudBibleReviews.
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.