Evidence standard
How Backup Power Finder tests portable power stations
A runtime result is useful only when the exact equipment, load, settings, elapsed time, and ending state are visible. This is the protocol every product-specific article and video must follow.
What counts as a test
A product page, specification sheet, or screen animation is a source—not a field test. A field test begins with the exact unit in frame and ends with a recorded outcome. Manufacturer claims may provide context, but they are never relabeled as observed results.
Every test record distinguishes three kinds of evidence: manufacturer specification, calculator estimate, and observed measurement.
Record the setup before the timer starts
- Exact power-station model, visible label, firmware or app version when relevant
- Battery age if known, starting state of charge, charging limits, and operating mode
- AC, DC, or USB output path and every adapter or cable in use
- Exact appliance or test load, its label, settings, and measured/displayed running watts
- Room or outdoor temperature and any fan, eco-mode, or display settings that can affect the result
- For solar: exact panel model, array configuration, orientation, shading, weather, and accepted input watts
Run battery and solar tests separately first
- 1Battery-only baseline
Start from the recorded charge, run the intended load without solar, and capture elapsed time plus ending charge.
- 2Startup behavior
Show whether the load starts normally, what the display reports, and whether the station trips, throttles, or changes modes.
- 3Solar-only input window
Record accepted watts at several times under documented conditions before mixing recharge into a runtime claim.
- 4Combined outage rehearsal
Only after the baselines exist, run the load and solar together against a defined outage target.
Publish the miss as well as the hit
The useful result is the difference between the estimate and observation. If a test ends early, the record should say why: inverter trip, low-battery shutdown, appliance cycle change, weak solar, user stop, or an uncontrolled condition.
Observed variance = (observed result − modeled result) ÷ modeled resultOne test does not prove a universal performance rate. It documents one unit, one load, and one set of conditions. Repeated tests can justify changing future planning assumptions; a convenient single result cannot.
Commercial relationships stay outside the measurement
If a product is borrowed, gifted, sponsored, or commissionable, that connection must be disclosed clearly near the review and relevant links. Compensation never changes the test protocol, the displayed result, or whether a failed result is published.
Backup Power Finder currently has no active affiliate links, sponsored tests, or merchant relationships.
Use the result to change the plan
After a valid test, update the calculator with the observed running watts, appliance schedule, and solar input. If the result already covers the outage target, stop shopping. If it misses, name the limiting constraint before comparing products.
Compare the observation to the model →Source register