Telegram RegisterThe public register of Telegram
Telegram profile photo for Logan Kilpatrick

Channel

Logan Kilpatrick

@OfficialLogan

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

1subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003989359717
TypeChannel
Username@OfficialLogan
DescriptionMember of technical staff, working on Gemini, @GoogleAIStudio, the Gemini API, & Kaggle. My views!
CreatedBetween 1 April 2026 and 8 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live2 September 2026
Measurements held2
On Telegramt.me/OfficialLogan

Growth

112 August 2026 — 1 subscribers15 August 2026 — 1 subscribers12 August 202615 August 2026
2 measurements spanning 3 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 10:011no change
12 Aug 2026, 13:481first reading

Engagement

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

What this channel posts

Photos
5
Videos
1

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3m 28s
Average length
3m 28s

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.

Recent posts

24 Jun 2026, 11:08 UTC13 viewsread 15 August 2026

Fun stat: In the last month, people have created more than 1,000,000 native Android apps directly in!! Huge amount of progress here and so cool to see the breadth of what folks are building.

24 Jun 2026, 11:07 UTC13 viewsread 15 August 2026

great work by and so many others across Google for making this API and getting us setup for the future!

16 Jun 2026, 18:32 UTC15 viewsread 15 August 2026

life is not happening in the future, it’s happening in the present

14 Jun 2026, 15:12 UTC16 viewsread 15 August 2026

Our long term goal for is to eliminate the friction to build with AI, then do the same for your own business, and ultimately unlock economic opportunity for everyone. Feels like early innings but I keep getting more excited about this.

14 Jun 2026, 15:11 UTC8 viewsread 15 August 2026

he would often opine about the serious of the mission, the stakes, how things felt at the time (to enjoy those moments) as things quickly shifted over time

14 Jun 2026, 15:11 UTC8 viewsread 15 August 2026

Great companies fail because they forget about creating great products

14 Jun 2026, 15:07 UTC8 viewsread 15 August 2026
Photo

Gemini Omni Flash is SOTA at image to video, text to video, and video editing : ) Excited to get this to developers in the API soon!

10 Jun 2026, 06:49 UTC4 viewsread 15 August 2026

try making an app yourself (we just launched Native Android App support along with Gmail, Docs, Calendar, and more!)

Showing the 12 most recent of 18 posts we hold for @OfficialLogan. 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 2 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 August 2026 — this entry's latest reading, not the date you are reading this.

“Logan Kilpatrick” (@OfficialLogan), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/OfficialLogan.

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.