Wisconsin Public Service seeks 15% residential rate increase
Summarised from 2 outlets · 7 reports · Updated 2 Oct, 13:01 · Archive
Wisconsin Public Service is seeking approval for a 15% rate increase for residential customers over two years.
Wisconsin Public Service (WPS) is seeking approval from state regulators for a 15% rate increase for residential customers spread across the next two years. The utility's proposal will be considered at a public hearing on Tuesday at Neville, where the Public Service Commission will hear input from the public on the request.

How it is being reported
- WPS proposes 15% rate increase over two years; PSC hears public inputWisconsin Public Service (WPS) is seeking approval from state regulators for a 15% rate increase for residential customers spread across the next two years.WSAW · 30 Sept, 16:39
- WPS Proposes 15% Rate Increase Over Two Years; PSC Hears Public InputWisconsin Public Service (WPS) is seeking approval from state regulators for a 15% rate increase for residential customers spread across the next two years.WBAY · 30 Sept, 01:26
- WPS proposes 15% rate increase over two years; PSC hears public inputThe utility wants to raise residential rates 15% over two years.WSAW · 30 Sept, 00:08
- WPS proposes 15% rate increase over two years; PSC hears public inputThe utility wants to raise residential rates 15% over two years.WBAY · 29 Sept, 23:27
- Public hearing on WPS rate hike request Tuesday at NevilleThe utility wants to raise residential rates 15% over two years.WSAW · 29 Sept, 15:01
- Public hearing on WPS rate hike request TuesdayThe utility wants to raise residential rates 15% over two years.WSAW · 29 Sept, 15:01
- Public hearing on WPS rate hike request Tuesday at NevilleThe utility wants to raise residential rates 15% over two years.WBAY · 29 Sept, 12:40
In this story: Wisconsin Public Service · Public Service Commission
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)