Telegram RegisterThe public register of Telegram
Telegram profile photo for Otto BASE Deployments

Channel

Otto BASE Deployments

@OttoBASEDeployments

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

1,925subscribers

-15 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001950072056
TypeChannel
Username@OttoBASEDeployments
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/OttoBASEDeployments

Growth

1,9251,9401,932.57 August 2026 — 1,940 subscribers7 August 2026 — 1,940 subscribers8 August 2026 — 1,939 subscribers11 August 2026 — 1,934 subscribers14 August 2026 — 1,933 subscribers18 August 2026 — 1,925 subscribers7 August 202618 August 2026
6 measurements spanning 11 days, net -15. 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,923–1,942 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 05:041,925-8
14 Aug 2026, 21:151,933-1
11 Aug 2026, 14:421,934-5
8 Aug 2026, 07:331,939-1
7 Aug 2026, 12:021,940no change
7 Aug 2026, 11:581,940first reading

Engagement

40 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.068%
avg views ÷ 1,925 subscribers
Avg views / post
1.3
40 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
40
of 40 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held40 (7 August 20267 August 2026)
Views total52
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:05 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

7 Aug 2026, 18:04 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ BlockchainFX (BlockchainFX) 🔖 0xE1911113593c613C1bDde809D8FF7CD8C4d5E483 Token Details: 🔗 Chain: BASE 📃 Contract: 0xE191...E483 🪙 Supply: 100000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x60f238d6...a8871580 🪪 Deployer Address: 0xd933...f416 💰 Deployer Balance: 0.0209 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:55 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ iotJ (IOT) 🔖 0x2217E5216b9793F076171acDdF73EA42511cbeeC Token Details: 🔗 Chain: BASE 📃 Contract: 0x2217...beeC 🪙 Supply: 100000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x0e9d6fb4...fc10169f 🪪 Deployer Address: 0x7fa6...3094 💰 Deployer Balance: 0.0006 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:54 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ BlockchainFX (BlockchainFX) 🔖 0x08f7Caee5D19a7b71C9B4426341f6191f324d1fa Token Details: 🔗 Chain: BASE 📃 Contract: 0x08f7...d1fa 🪙 Supply: 100000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xa26f7654...b8bb6acf 🪪 Deployer Address: 0xf6a2...d6c2 💰 Deployer Balance: 0.0231 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:49 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ M2M Protocol Token (M2M) 🔖 0x691e9DD00Fc6Ec054598bbFe84bb402bbfBf2394 Token Details: 🔗 Chain: BASE 📃 Contract: 0x691e...2394 🪙 Supply: 10000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xf1cbc25f...8aad83db 🪪 Deployer Address: 0x31d3...3e35 💰 Deployer Balance: 0.0000 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:48 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ EXPLO (EXPLO) 🔖 0xC6970E3797491aa076039d3c0A2CD39405Cc9542 Token Details: 🔗 Chain: BASE 📃 Contract: 0xC697...9542 🪙 Supply: 9400000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xc8a4411e...a37901d5 🪪 Deployer Address: 0x9235...e29e 💰 Deployer Balance: 15.0200 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:47 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ hNaNb (HNA) 🔖 0x2322725012A9d8Efdb24479Fa53bc137FE937dee Token Details: 🔗 Chain: BASE 📃 Contract: 0x2322...7dee 🪙 Supply: 10000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xf735e47a...b5ab4241 🪪 Deployer Address: 0x5a49...0abb 💰 Deployer Balance: 0.0009 ETH 🏦 Initial Funding: 0x4e3a...1B60

7 Aug 2026, 17:46 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ wrPNkr (WRP) 🔖 0x25518EbA29Bf9A4E7B12700EC85AB084C52294C2 Token Details: 🔗 Chain: BASE 📃 Contract: 0x2551...94C2 🪙 Supply: 10000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x30179f7b...f61b27ad 🪪 Deployer Address: 0xab60...c7a9 💰 Deployer Balance: 0.0005 ETH 🏦 Initial Funding: 0x4e3a...1B60

7 Aug 2026, 17:44 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ PepeKing (PEPKING) 🔖 0x5da44843F90068376E508f5A00f3DF91C28336aF Token Details: 🔗 Chain: BASE 📃 Contract: 0x5da4...36aF 🪙 Supply: 5600000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xba005b82...d9747390 🪪 Deployer Address: 0x3e1f...e91e 💰 Deployer Balance: 2.5070 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:41 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ BaseBasicToken (BBT) 🔖 0x50aa910B908F94910A298624C6F9C136f021f069 Token Details: 🔗 Chain: BASE 📃 Contract: 0x50aa...f069 🪙 Supply: 1000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xbd7b706e...01d3e144 🪪 Deployer Address: 0x2fc1...f4e8 💰 Deployer Balance: 0.0007 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:41 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ Soas Oil Supply (SOAS) 🔖 0x0C10C8eab05b2aB762FF0A39ef27fbF9F4fB31Ed Token Details: 🔗 Chain: BASE 📃 Contract: 0x0C10...31Ed 🪙 Supply: 1000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x91ffae16...9b230571 🪪 Deployer Address: 0x436e...69e8 💰 Deployer Balance: 0.0016 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:34 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ ICM.FUN (ICM) 🔖 0xeCdFf6f83863252524F341aF046B475A1d55a3aD Token Details: 🔗 Chain: BASE 📃 Contract: 0xeCdF...a3aD 🪙 Supply: 1000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xbbae5e44...ef20ea9e 🪪 Deployer Address: 0xd4e5...826b 💰 Deployer Balance: 12.2684 ETH 🏦 Initial Funding: -

7 Aug 2026, 17:34 UTC1 viewsread 7 August 2026

New BASE Token Deployment 🏷️ viS (VIS) 🔖 0xbf979191051FB1c5Bf5d5C2c9a99BB51f2cf6a05 Token Details: 🔗 Chain: BASE 📃 Contract: 0xbf97...6a05 🪙 Supply: 100000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xcbf28c01...4932d181 🪪 Deployer Address: 0xf96b...e09a 💰 Deployer Balance: 0.0009 ETH 🏦 Initial Funding: 0xA5E8...2618

Showing the 12 most recent of 40 posts we hold for @OttoBASEDeployments. 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 — 959,584 of 1,549,704entries 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Otto BASE Deployments” (@OttoBASEDeployments), 1,925 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/OttoBASEDeployments.

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.