Telegram RegisterThe public register of Telegram
Telegram profile photo for BENJAMIN SUULOLA MINISTRIES

Channel

BENJAMIN SUULOLA MINISTRIES

@benjaminsuulola

On this record: Growth · Engagement · Posts · Cite this entry

201subscribers

+1 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-1001311584502
TypeChannel
Username@benjaminsuulola
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/benjaminsuulola

Growth

199202200.57 August 2026 — 200 subscribers8 August 2026 — 199 subscribers8 August 2026 — 199 subscribers16 August 2026 — 201 subscribers25 August 2026 — 200 subscribers31 August 2026 — 199 subscribers9 September 2026 — 202 subscribers17 September 2026 — 201 subscribers2017 August 202617 September 2026
8 measurements spanning 41 days, net +1. 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 199–202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 17:20201-1
9 Sept 2026, 20:36202+3
31 Aug 2026, 15:53199-1
25 Aug 2026, 01:56200-1
16 Aug 2026, 18:16201+2
8 Aug 2026, 11:33199no change
8 Aug 2026, 11:25199-1
7 Aug 2026, 20:23200first reading

Engagement

11 posts held, back to 27 July 2026the 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 11 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Aug 2026, 10:02 UTC12 viewsread 8 August 2026
Photo

🔥 7 COVENANT NIGHTS OF FRESH FIRE 2026: THANK YOU, JESUS! 🔥 The fire has fallen, and our victory is sealed! We give all the glory to Jesus for an explosive 7 days of raw power, heavy impartations, and broken chains. Our altars are ablaze, and our testimonies have just begun! 💥🪵 A massive thank you to our beloved father, Pastor Gbenga Oyedapo, and all our anointed guest ministers for fueling the fire. To everyone

28 Jul 2026, 22:01 UTC18 viewsread 8 August 2026

We're Live Now for Fresh Fire 🔥 Day 4 | 7 Covenant Nights 2026

27 Jul 2026, 14:10 UTC22 viewsread 8 August 2026
Photo

🔥 Quote Excerpts from Night 2 of 7 Covenant Nights of Fresh Fire 2026 by Pastor Benjamin Oladokun 🔥

Showing the 11 most recent of 11 posts we hold for @benjaminsuulola. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“BENJAMIN SUULOLA MINISTRIES” (@benjaminsuulola), 201 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/benjaminsuulola.

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.