Can confirm the same behaviour. Maybe the documentation is wrong and a random timestamp is meant?

I don't think it's a documentation bug, postman uses the same variable: https://learning.postman.com/docs/tests-and-scripts/write-scripts/variables-list/. Also, there are 3 other variables ({{$randomDate*}}) for random timestamps.

Same problem with normal timestamp. It also give back time in the future :-)

I need the unix time stamp for authorization against one of our api servers.

Currently we are using random time to generate this

 timestamp: () => faker.date.anytime().getTime().toString(),
  isoTimestamp: () => faker.date.anytime().toISOString(),

see https://github.com/usebruno/bruno/blob/main/packages/bruno-common/src/utils/faker-functions.ts
will get this updated

@sww-jm
I use this little Pre Request script:

function getCurrentTimestamp() {
  return new Date().getTime();
}

bru.setVar("currentTimestamp", getCurrentTimestamp());

You then can use {{currentTimestamp}} in your requests.

If you add the following lines to the Pre Request script you can see the difference to {{$timestamp}} in the Developer Tools console:

bru.setVar("myTimestamp", "{{$timestamp}}");

console.log(bru.getVar("currentTimestamp"))
console.log(bru.getVar("myTimestamp")) 

ah, very nice! (and dividing by 1000 to get the timestamp in seconds totally makes sense)

maybe you could add a new variable "timestamp_ms" which contains the timestamp in milliseconds?
(this could be useful if consecutive requests in a fast succession need a unique timestamp)