Telegram RegisterThe public register of Telegram
Telegram profile photo for adapter

Channel

adapter

@BikiniBottomadp

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

201subscribers

-6 since we began measuring on 13 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003824359660
TypeChannel
Username@BikiniBottomadp
Created18 March 2026measured — dated from the channel’s first post
First recorded13 September 2026
Last confirmed live15 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/BikiniBottomadp

Growth

20120720413 September 2026 — 207 subscribers13 September 2026 — 207 subscribers15 September 2026 — 201 subscribers13 September 202615 September 2026
3 measurements spanning 2 days, net -6. 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 200–208 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 06:54201-6
13 Sept 2026, 18:22207no change
13 Sept 2026, 17:47207first reading

Engagement

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

What this channel posts

Video runtime
16s
Average length
16s

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.

Reaction mix

223 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 57.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12957.8%
custom 52603833188761109114922.0%
custom 5260234330755578976219.42%
custom 5260486342256639903177.62%
52.24%
❤‍🔥10.448%
💘10.448%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 7 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 223 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 18 March 2026 to 1 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

1 Aug 2026, 18:56 UTC≈2,480 views10 reactionsread 13 September 2026
Photo

🤩🥰 Официально объявляем союз! 🤩🤩@BikiniBottomAdp 🤩🤩@adptKZH

10

26 Jul 2026, 12:00 UTC≈2,970 views14 reactionsread 13 September 2026
Photo

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🦴 ☺️☺️☺️☺️☺️☺️☺️☺️☺️☺️ объявляем СОЮЗ. 🌟 @BikiniBottomAdp &@adptZhasaTaĺk 🦢🦢 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟

14

22 May 2026, 21:39 UTC≈7,230 views30 reactionsread 13 September 2026
Photo

Официально объявляем союз! 🤩@BikiniBottomadp 🤩@adapterDRK 🤩@adptPRX 🤩 @serious_adapt

30

1 May 2026, 05:56 UTC≈7,820 views31 reactionsread 13 September 2026
Photo

Photo, posted without a caption

31

29 Apr 2026, 20:00 UTC≈7,300 views32 reactionsread 13 September 2026
Photo

форсаж 1 форсаж 2 форсаж 3

32

27 Mar 2026, 17:16 UTC≈7,700 views46 reactionsread 13 September 2026
Sticker

Sticker, posted without a caption

custom 5260383318876110911219custom 52602343307555789769custom 52604863422566399037

27 Mar 2026, 17:16 UTC≈8,130 views60 reactionsread 13 September 2026
Video

Bikini Bottom chat Adapter😎 🤍link: 🤍rules for chat: BikiniBottom. BB rules 🤍archive: 🤍tt chat: Bb archive. Bb tt chat

custom 526038331887611091128custom 526023433075557897612custom 52604863422566399031053❤‍🔥1💘1

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

Mentions

Named by 4 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.

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

“adapter” (@BikiniBottomadp), 201 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/BikiniBottomadp.

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.