Anker 300W Power Bank Wattage Budget & Gear Charge Simulator
300W MAX SIMULTANEOUS DISCHARGE
Device Patch Bay4 PORTS ACTIVE
Based on Kotaku's deal report: "Enough Ports for Your iPhone 18 Pro, AirPods 5, and One More Device". Connect handhelds, MacBooks, and high-draw peripherals up to the 300W limit.
Simultaneous Load TelemetrySYSTEM ACTIVE
All connected devices receiving full negotiated USB-PD wattage.
Allocated Power
230W
of 300W Max Rating
Headroom Left
70W
Free Port Budget
Efficiency Status
Optimal (76.7% Load)
GaNPrime Inverter
Thermal Index
Normal Operating Range
Active Temp: 38.4°C
230W
TOTAL DRAW
Port
Device
Profile
Draw
Status
Theoretical Battery Runtime (99.6Wh Cell): ~26 mins at current 230W draw
Summary copied to clipboard!
Priority cuts and labels in a shared watt budget
Read the explanation
The saved default fixture requests forty-five, fifteen, one hundred forty and thirty watts across four ports. They sum to two hundred thirty, below the shared three hundred watt budget, leaving seventy. Bars compare demand with budget at two pixels per watt. The displayed seventy-six point seven percent is this load divided by the configured budget; it is not measured conversion efficiency. Device and deal names are saved labels, not verified current hardware specifications. The stored ninety-nine point six watt-hour battery field does not enter this power-allocation function, so this tool does not estimate battery runtime. The overload preset requests one hundred forty, sixty-five, one hundred forty and thirty watts. Despite its button wording, these sum to three hundred seventy-five. All requests already fit their individual port caps, but the shared limit requires cutting seventy-five. The function sorts descending priority numbers: it removes thirty from the USB-A port, then forty-five from the second USB-C, leaving twenty there while the two priority-one ports keep one hundred forty each. Bars compare requested and allocated totals at one point five pixels per watt. This is the source allocation rule, not observed physical negotiation. The exported supported flag becomes false. The gaming preset requests one hundred forty, forty-five, one hundred and fifteen watts, totaling exactly three hundred. No aggregate cut occurs. The overload preset also ends with three hundred after cuts. Both cross the source label threshold above two hundred eighty and display thermal throttling active, even though gaming is not marked is_throttled. Equal bars show both allocated totals at one point five pixels per watt. The thermal text is a threshold classification and does not apply another reduction or measure temperature. Native overload action, complete JSON export and return to the default fixture preserve this distinction without repairing source labels or claiming hardware validation.