GPT usage remaining calculator

1. Open the usage panel or usage settings for the exact account and service you are using. For OpenAI, follow the usage-dashboard link in the official usage guidance. This BusCalc page does not log in, connect to your account, or detect your balances.
2. Choose only the limits your own dashboard actually shows: weekly, five-hour, or both. Not every plan has both limits, and ordinary ChatGPT chat limits may differ from Codex or ChatGPT Work limits. Do not invent a missing limit.
3. Read the remaining percentage for each applicable allowance. If the panel explicitly shows percentage used, subtract it from 100: 97% used means 3% remaining. Confirm what the provider’s label means.
4. Record the time until each reset from the provider’s dashboard. Enter hours from the current reading: 2 hours 15 minutes = 2.25; 2 days 6 hours = 54. Do not enter “5” simply because it is called a five-hour limit. If reset is due now, refresh the provider readings first.
5. Do not enter a password, API key, account identifier, project information or credit-card details. None is needed.

1. Before a normal block of work: write down the time and remaining weekly/five-hour percentages. These become the earlier snapshot values.
2. Complete a countable block of similar work using the same account, model, settings and general context size. You do not need to spend extra usage just to test this tool. A normal 15–30 minute work block can be a starting point, but a small sample with no visible percentage change is not enough to estimate allowance cost reliably.
3. Count comparable work units completed. You define a unit: one similar request, one similar code-review task, or one complete work session. If the sample was one complete session, enter 1; the estimate will then be in similar sessions, not messages. Two very different tasks are a weak sample for predicting a third.
4. After that block: refresh the provider usage display, note the time, remaining percentages and updated time until reset. These are the current values. Enter the elapsed wall-clock minutes between the two readings, including any idle time.
5. Confirm that neither allowance reset and that the allowance basis did not change. Discard the sample after a reset, plan/promotion change, or switch to purchased credits. A balance that increased is a clear warning; a reset can also be hidden by subsequent usage, so the calculator cannot detect every invalid sample automatically.
6. Other chats, background agents, devices, applications or team activity may draw from the same allowance. Pause unrelated activity if possible, or count its work too. Otherwise the observed consumption cannot be attributed only to the work units you entered.

Keep the sample within the same reset periods. Do not combine one earlier reading from yesterday’s five-hour period with a current reading after that limit refreshed. Longer, representative samples can reduce rounding noise, but must not cross a reset.

Estimate similar work remaining from two snapshots

Enter the current remaining percentage and current hours until reset for each limit, followed by its earlier remaining percentage. Enter minutes between snapshots and the number of completed comparable work units. Confirm the unchanged reset periods. Select the display-rounding assumption that matches your readings.

Reserve: this is the number of percentage points of the full allowance you want to keep. With 3% remaining and a 1-point reserve, only 2 points are spendable. Zero means no reserve. A reserve is a planning target; the calculator does not enforce it in your provider account.

Precision: “Rounded to nearest whole percentage point” assumes an uncertainty of half a point at each reading. For example, two readings differing by only one displayed point can hide a true drop anywhere from roughly zero to two points. This assumption is not a verified statement of how your provider rounds or updates its display. “Exact” treats your entries as exact for arithmetic; it does not make future usage predictable.

Current balances only — no work estimate

Enter current balances, reserve targets and hours to reset. You receive remaining/used shares and an average percentage-point pace that would spread the spendable balance across the time left. This method deliberately does not invent work hours, token totals or request counts. Time passing alone does not consume the allowance at that pace.

What-if forecast using my own consumption rates

Enter a separately measured or assumed rate in percentage points per elapsed hour for each allowance. A rate of 2 means two points of that full allowance per hour, not 2% of the remaining balance. Enter the planned elapsed work interval. The tool shows at-rate time and projected balances up to the earlier of your requested interval or the first applicable reset. It does not estimate work-unit counts without a sample count.

Illustrative data only—not your account’s measured usage. Suppose you completed two similar work units over 30 elapsed minutes, with no reset or allowance change:

• Weekly earlier reading: 4% remaining; current reading: 3% remaining.
• Five-hour earlier reading: 89% remaining; current reading: 79% remaining.
• At the current reading, weekly reset is 48 hours away and five-hour reset is 2 hours away.
• Completed comparable work units: 2. Reserve for both allowances: 0.

The sample used 1 weekly point and 10 five-hour points. Dividing by two units gives average costs of 0.5 weekly point and 5 five-hour points per unit. At those point estimates, the weekly balance can fund 6 similar units and the five-hour balance can fund 15 whole units. The sample pace was 4 units per hour, so only 8 units fit in the 2 hours before the first reset. The joint point estimate is the smallest of those ceilings: 6 similar units, or about 1.5 hours at the sample activity pattern, before the weekly balance reaches zero.

If the percentages are treated as rounded to the nearest whole point, the work estimate is much less precise: the same example allows a rounding-only range of 2–8 units before a reserve or the first reset. That is not a statistical confidence interval, and actual future work can fall outside it. The range does not cover workload changes, delayed provider accounting or other account activity.

Select Load example for this method to reproduce the numbers. Replace all example values before using the result for your own planning.

These two readings show a drop of 1 weekly percentage point and 6 five-hour points. If you treat everything between the readings as one comparable block of work, the current weekly balance has a point-rate budget for 2 more such blocks; the current five-hour balance has a budget for 12 whole such blocks (73 ÷ 6, rounded down). The weekly budget is tighter under that same-work/no-refill assumption.

Without the elapsed time and reset information, this comparison cannot say how long those blocks take, whether they fit before a reset, or how the balances change afterward. Whole-percentage display rounding can make a one-point weekly drop particularly uncertain. Do not enter an invented duration merely to obtain an hours result. For a complete forecast, start a new timed sample and use the dashboard reset times at its end.

• Estimated similar work units: a whole-unit point estimate capped by each allowance’s spendable balance and by time until the first reset at the sample pace. It is an estimate of work like your sample—not a fixed message entitlement.
• Consumption rates: the percentage-point decrease divided by elapsed hours, separately for each allowance.
• Average cost per work unit: each allowance’s observed decrease divided by the completed work units you counted.
• First limiting allowance: whichever reaches its reserve first at the entered/observed rates, before the first reset. The tool does not choose this by taking the smaller remaining percentage.
• Same-pattern time: estimated elapsed time until a reserve or the first reset. It includes the sample’s idle/activity pattern; it is not a promise of continuous active model execution.
• Rounding bounds: optional low/high work-unit estimates and time bounds under the selected display-rounding assumption. “Not bounded” means the lower plausible rate includes zero, not unlimited usage.
• Graph: point-rate projected percentages from now to the first reset or shorter planned endpoint. Each line is a percentage of its own allowance; the lines do not represent equal token or work capacities. The graph does not update from your account.

Recalculate after a substantial block of work, before starting a large job, when a reset occurs, or when the model, reasoning/speed setting, context size or task type changes. Newer representative samples are usually more useful than reusing an old rate. A zero visible change means there may be too little measurable consumption to estimate work left; it does not prove the work was free.

Large tasks can cost more than previous ones. Caching, tools, context growth, reasoning, parallel jobs and accounting updates can change consumption. The calculator does not convert percentages into tokens, dollars, API credits or guaranteed messages. It does not predict future resets/refills, enforce reserves, read account data, purchase credits or override a limit. It stops the joint forecast at the first entered reset because the next allowance state is not known. Purchased-credit balances and unrelated quotas are not modeled.

Entries remain in your browser tab and are not saved automatically. Print or download the result if you want a record. The result file contains your entered readings and calculated results; it is not an editable account connection or a live monitor. Use the provider dashboard as the source of truth.