Skins. Codes. Clear answers.

Guides/Codes & offers

Codes & offers

Calculate an offer’s elapsed-hour timestamp

Add a stated number of elapsed hours to a timestamp with Z or a UTC offset. Read the result in UTC and your browser’s local time, then compare it with the offer’s actual terms.

3 min read
Published Revised

THE QUICK ANSWER

This tool adds elapsed hours to the starting instant you supply. It does not establish when an offer starts, whether you qualify or which deadline the operator applies.

01

Enter the stated start and duration

Use the starting event named in the written offer, such as activation or a qualifying action. Enter its complete timestamp with Z or an explicit offset, then the stated number of elapsed hours.

The form accepts 0 to 8,784 hours in quarter-hour increments. A quarter hour is 0.25; do not enter 0.15 to mean fifteen minutes. If the offer gives a fixed end date instead of an elapsed duration, read that date directly rather than inventing a starting rule.

STRIKEPOT / EXPLAINED

Turn a written duration into an instant

  1. Start event

    Use the exact event and offset named by the offer.

  2. Elapsed hours

    Enter the stated duration, such as 24 or 0.25.

  3. UTC result

    Compare the calculated instant with the operator’s written condition.

Original explanation of the form’s arithmetic; a calculation does not verify an offer rule.

Original explanation · not an account screenshot

Try it with your own details.

This tool keeps your input in this page. It does not upload it, add it to the address or save it. Downloads happen only when you choose them. Reset the form when you finish.

02

Use the supported timestamp format

Enter YYYY-MM-DDTHH:MM:SSZ or a value ending in an offset such as -04:00. Whole seconds are optional; the date, T, time and zone are required. Fractional seconds, time-zone abbreviations and date-only entries are outside this form.

An offset identifies the supplied instant. The calculation then adds real elapsed hours; it is not a rule to keep the same wall-clock time across a daylight-saving change. The browser-local result depends on your device’s current time-zone setting.

Illustrative 24-hour calculation
Entered start2026-10-23T18:00:00-04:00
Start in UTC2026-10-23T22:00:00.000Z
After 24 elapsed hours2026-10-24T22:00:00.000Z. This is example arithmetic, not an offer’s verified expiry.

03

Compare the calculated instant with the actual terms

The result shows the UTC start, the UTC end after your entered hours and your browser’s local time for that end. Use the UTC value when two people have different device time zones.

A correctly calculated instant does not resolve an unclear condition. Claiming an offer, using a reward and completing a qualifying action can have different deadlines. Keep the wording that supplied your start and duration beside the result.

STRIKEPOT / EXPLAINED

Two time statements need different calculations

  1. 24 elapsed hours

    Add a fixed duration to an instant.

  2. Three business days

    Count dates under an explicit weekend and holiday rule.

  3. Fixed published deadline

    Read the published end instant and its zone.

This comparison prevents an elapsed-hours form from silently replacing a different timing rule.

Original explanation · not an account screenshot

04

Save the result with the written condition

Download promotion-timestamp.txt if you need a record of the input start, calculated UTC timestamp and elapsed hours. It does not include or validate the operator’s full terms; retain those separately.

If support gave a business-day estimate, use a business-day calendar with its stated exclusions instead. Adding 72 elapsed hours is a different operation from counting three weekdays. The tool does not save or upload your input. Use Reset this form when you finish.

BEFORE YOU CONTINUE

Quick checklist

  • Identify the exact starting event in the terms.
  • Enter Z or a numeric UTC offset.
  • Use quarter-hour decimal values for elapsed hours.
  • Keep the written condition with the UTC calculation.

Official sources

Tool behaviour was checked against StrikePot’s form and browser implementation on 26 October 2026 (America/Toronto). The external references below explain the relevant formats and source records.

Implementation inspected: deadline form, gtTimestamp, gtNumber, gtDeadline and the deadline result/download handler. Quarter-hour increments are enforced by the form; the helper adds elapsed milliseconds. The start trigger, eligibility and official expiry are not obtained from a provider. No offer activation, account check or live deadline was tested. Example timestamps are arithmetic examples.

KEEP READING

A useful next read.

All guides

Codes & offers · 2 min read

Read the important conditions

Before relying on a promotion, check who qualifies, the required action, both claim and use deadlines, and any restrictions on the reward.

Read guide

Codes & offers · 2 min read

A code is not working

Save the exact code and rejection message, then check whether the issue concerns spelling, an existing referral, eligibility or a missing reward.

Read guide

Support · 3 min read

A better support ticket

Include the affected order or trade, the exact status and a dated timeline. Use the template to explain what happened and ask for the next step.

Read guide