LinkedIn Post Date Extractor
Paste a LinkedIn post, comment, or activity URL. Get the exact second it went up, worked out in your own browser. The URL never leaves your machine, unless it is an lnkd.in short link, which our server expands first.
Decoded in your browser. A lnkd.in short link is expanded on our server first, then decoded here.
You found the date. The next post is the harder bit.
Oiti reads what you have already published and writes from it, so the first draft already sounds like the rest of your posts.
LinkedIn tells you a post is "2mo ago" and leaves it at that. Which is fine while you're scrolling, and no use at all when you're trying to establish whether a claim landed before or after the thing it's about.
The exact time isn't hidden anywhere clever. It's sitting in the URL. Every post, comment, and share gets an ID the moment it's created, and the top of that ID is a millisecond clock reading. Paste the link and this page reads it back, offline, in the tab you already have open.
How to use it
Three steps, no account, and nothing leaves your browser.
- 1
Copy the link
On the post, open the three-dot menu at the top right and choose "Copy link to post". For a comment, the three-dot menu on the comment itself has "Copy link to comment".
- 2
Paste the link
Paste it in the box above and press Get the date.
- 3
Read the answer
You get the time in your own timezone, the same moment in UTC, an ISO 8601 stamp and a Unix number for spreadsheets, and how long ago it was. Copy whichever one you need.
Where the date actually comes from
A LinkedIn ID is a 19-digit number and it isn't random. The bottom 22 bits are a counter, there to stop two things minted in the same millisecond from colliding. Everything above that is the time, in milliseconds since 1 January 1970. Shift the number right by 22 places and the clock reading falls out.
Which is why the lookup needs no login and never touches LinkedIn. There's nothing to fetch. The answer is already in the link you pasted.
We checked this rather than trusting the folklore, because the whole product is one arithmetic operation and it had better be the right one. LinkedIn publishes a datePublished field in the page data of any public post. We decoded six posts and comments spanning 2023 to 2026 and compared. Comments matched to the millisecond, exactly. Posts landed within 30 milliseconds of LinkedIn's own figure. Then ten more posts, June 2022 through August 2026, checked against the dates Google has indexed for them: nine matched outright, and the tenth turned out to be a timezone offset rather than a bad decode.
Why the same post can have two different times
Most posts carry more than one ID, and they don't all mean the same thing.
A post can carry a ugcPost ID and an activity ID. On every post we checked, the activity ID matched the moment LinkedIn itself gives as the publish time. The ugcPost ID was either that same moment or earlier, and usually earlier by milliseconds, which is why nobody has noticed. Sometimes it's earlier by a lot.
A company post from 19 June 2026 carries a ugcPost ID decoding to 02:31:33 UTC and an activity ID decoding to 07:30:01 UTC. LinkedIn's own page data puts the publish time at 07:30:01. Five hours between the two, on one post. We can't see inside LinkedIn to tell you exactly why, but a post written the night before and scheduled for the morning would look precisely like that.
Every other extractor we tested reads whichever ID it happens to find and calls that the publish date. One prints a scheduled post's drafting time under the heading "parent post date" and says nothing about the gap.
So this tool tells you which ID it read. If your link carries a ugcPost or a share ID you get a note saying so, because that time can be earlier than the moment anyone saw the post. Need the publish time exactly? Open the post on LinkedIn and copy the link from the post's own three-dot menu. That one carries the activity ID.
What this tool will not do
There's no author name here, no post text, no reaction counts, because we never fetch the post. Tools that show you those are loading the page from a server somewhere, and half those fields come back empty anyway for anything LinkedIn hides from logged-out visitors. We'd rather keep the promise at the top of this page than ship a table full of N/A.
An lnkd.in short link is the one input this page can't answer on its own. A short link is a code with nothing encoded in it, so our server asks LinkedIn where it points and hands the full address back. The date is then decoded here, in your browser, like every other input.
Pulse articles are out of reach for a different reason: LinkedIn articles use a slug URL with no number in it, so there's nothing to decode. Profile and company page links, same.
Edits are invisible to this. The ID gets minted once, at creation, and editing a post doesn't mint a new one, so an edited post still reports its original moment.
The rest of the free set lives on the Oiti free tools hub.
Frequently asked questions
- Can you really see the exact time a LinkedIn post was published?
- To the second, yes. LinkedIn's interface rounds everything down to a relative label like "3w ago", but the precise creation time is encoded in the post's ID, and that ID travels in every link. Reading it back takes one arithmetic operation and no access to the post itself.
- How do I get a LinkedIn post's URL?
- On the post, click the three-dot menu at the top right and choose "Copy link to post". For a comment, the three-dot menu on the comment has "Copy link to comment". Both work here. A post link also works in the LinkedIn video downloader, if the post has a video.
- Is anything sent to a server?
- Only an lnkd.in short link, and only to find out where it points. A short link carries no ID, so our server reads the address it redirects to and hands that back; nothing about it is stored or logged. Every other input is decoded in JavaScript in your tab. Open your browser's developer tools, switch to the Network tab, and paste a full post URL. Nothing fires.
- Does the person know I looked up their post's date?
- A full post URL is decoded in your tab, so nothing is requested from LinkedIn at all. A short link is expanded from our server rather than from you. Neither one is a profile view and neither shows up in anybody's activity.
- Why doesn't the date match the "2mo ago" that LinkedIn shows me?
- Because that label is rounded, and it keeps drifting as time passes. A post labelled "2mo ago" sits somewhere in a window several weeks wide. The decoded timestamp is a fixed moment and doesn't move.
- Does it work on comments?
- Yes. Paste a comment link and the comment's own time is the headline answer, with the parent post's time underneath so you can see the gap between them. Comment IDs are encoded the same way as post IDs, and in our testing they matched LinkedIn's published values exactly, with no drift at all.
- Why does it sometimes say the time is when the post was created rather than published?
- Because that's what the ID in your link encodes. A post can carry more than one ID, and the kinds we label "created" have turned up earlier than the publish time, once by five hours. When your link carries one of those, we say so, instead of quietly presenting an earlier time as a publish time.
- Does it work on LinkedIn articles or profile links?
- It doesn't. Pulse articles and profile pages use text slugs with no number in them, so there's nothing encoded to read, and the tool will tell you that rather than guess.
- Does it work on old posts, or posts I can't open?
- Age makes no difference at all. A post from 2022 decodes as reliably as one from this morning. And since the date comes out of the link rather than the page, it still decodes for a post that's been deleted or made private, as long as you kept the URL.
Your writing, cloned.
Oiti picks up how you build a post from the ones you have already published, and it remembers what you change about its drafts. Scheduling and the numbers afterwards happen in the same place.