When exactly was this LinkedIn post published?
Wed, Jun 21 2023, 09:52:19 UTC, decoded from the 19-digit activity ID.
Link https://www.linkedin.com/feed/update/urn:li:activity:7077221689796784128/
The date is already in the link.
LinkedIn shows "2w" or "3mo". The post URL holds the exact time.
Part of social media monitoring
Paste full linkedin.com links, not lnkd.in short links. The four steps below show how the LinkedIn post date extractor method works, so you can check any result yourself.
Open in SpringBrandThis opens SpringBrand's assistant with your links and asks it to decode them. Each run spends credits from your balance.
Every LinkedIn post and comment ID contains the moment it was created. The LinkedIn post date extractor method reads that ID and turns it into a date and time in UTC and in your time zone.
START WITH A LINK
Each card is a link type the LinkedIn post date extractor handles. The steps below show where the ID sits in each one.
Wed, Jun 21 2023, 09:52:19 UTC, decoded from the 19-digit activity ID.
Link https://www.linkedin.com/feed/update/urn:li:activity:7077221689796784128/
Two times: when the post was created and when the comment was written. The comment ID is the second number.
Link A link that contains urn:li:comment:(activity:<post ID>,<comment ID>)
A date and time for each link, ready to paste into your spreadsheet.
Link One link per line for each post you want in the report.
This is the LinkedIn post date extractor method, step by step. It works in any desktop browser and takes about a minute for the first link.
On the post, open the three-dot menu and choose Copy link to post. For a comment, use the comment's own menu. If you only have an lnkd.in short link, open it first and copy the full linkedin.com address.
Look for the long number after activity:, share: or ugcPost:, or after -activity- in a /posts/ link. In a comment link there are two long numbers; the second one, inside comment:(…), is the comment.
The first 41 bits of the ID are a Unix time in milliseconds. In your browser console, run new Date(Number(BigInt("7077221689796784128") >> 22n)).toISOString() with your ID in place of the example.
The result is in UTC: the example returns 2023-06-21T09:52:19.268Z. Convert it to your time zone, and round to the second; that is the precision the LinkedIn post date extractor method supports.
WHAT IT HANDLES
Most LinkedIn URLs for posts and comments carry an ID with a timestamp inside. A few link types do not, and a LinkedIn post date extractor cannot read a date from them.
01 / POSTS
Links with activity:, share: or ugcPost: IDs, /posts/ links and bare 19-digit IDs all decode. The same post can have an activity ID and a share ID a fraction of a second apart; both give the same date.
URL-encoded links such as urn%3Ali%3AugcPost%3A decode too once the encoding is removed.
/feed/update/urn:li:activity:…
/posts/name-activity-…
urn:li:share: and urn:li:ugcPost:
A bare 19-digit ID
02 / COMMENTS
A comment link carries the post ID first and the comment ID second. Read the second number for the comment time. A reply link carries both a comment and a reply ID; the larger one is the reply.
Reading only the first long number gives you the post time, not the comment time, and nothing on the page tells you it is wrong.
First number: the post
Second number: the comment
Largest number: the reply
03 / NO DATE IN THE LINK
lnkd.in short links, Pulse articles, profile, company and group pages carry no post ID. Job links have a short ID with no timestamp, so the date a job was posted cannot be read this way.
Pulse articles print their publish date on the page itself.
lnkd.in short links
Pulse articles
Profiles, company pages, groups
Job posts
LinkedIn shows relative times such as "2w" on profile posts. People compiling reports and checking claims need the exact date. We checked the method against LinkedIn's own published dates on 2026-11-18.
Checked on
Profile posts show relative times by design. Anyone building a list of past posts runs into this, which is the main reason people search for a LinkedIn post date extractor.
“I'm compiling a list of our posts from previous months and it's only showing 1 month, 2 months, and not the exact date.”
Source: r/linkedin: exact posting date
Not for posts shared from member profiles, according to a reply in the same thread. The ID in the URL is the reliable route.
“At the moment, we don't offer a way to view or export exact publish dates for posts shared from individual member profiles. Profile posts display relative timestamps by design”
On a public post, the decoded activity ID was 36 milliseconds from the datePublished value on the post page; five comments on the same post were within 1 millisecond. Two samples from LinkedIn's Posts API documentation were within 225 milliseconds of their createdAt values. Treat the result as accurate to the second.
Source: LinkedIn Posts API documentation (createdAt samples)
Several sites offer a LinkedIn post date extractor. The table compares what each tool's own page says. Where a page did not say, we wrote that instead of guessing.
| Tool | Links per run | Comments | lnkd.in short links | Where it runs |
|---|---|---|---|---|
| This page's method | Any number, one at a time | Yes, comments and replies | No, open the full link first | Your own browser |
| Trevor Fox | 1 | Yes | Yes, resolved on its server | Its server reads the public page |
| OpenTweet | Up to 500 | Not stated on the page | Not stated on the page | In your browser |
| HyperClapper | Up to 300, with CSV download | Yes, comments and replies | Not stated on the page | In your browser |
| ContentIn | 1 | No, says comments are not supported | Not stated on the page | Not stated on the page |
Checked 2026-11-18 from each tool's public LinkedIn post date extractor page. "Not stated" means the page did not say, not that the feature is missing.
A FEW THINGS TO KNOW