BIZTRAC BETA
Business and other management consultancy activities

POW HOLDING AS

Org. no. 911817357 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 433,000
Operating profit NOK 427,000
Equity NOK −104,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−104k kr).

POW HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 911817357. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å investere og eie aksjer i andre selskap, samt drive rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 433,000 in revenue and NOK 427,000 in operating profit.

Key figures · 2024

Revenue
NOK 433,000
Operating profit
NOK 427,000
Equity
NOK −104,000
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns POW HOLDING AS?

PER OTTO WIGUM
POW HOLDING AS
NOK 433,000 rev. · NOK 427,000 profit

POW HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does POW HOLDING AS own?

POW HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about POW HOLDING AS

Who owns POW HOLDING AS?

PER OTTO WIGUM is the largest registered owner, with 100.0%.

What is the revenue of POW HOLDING AS?

POW HOLDING AS had revenue of NOK 433,000 in 2024.

Where is POW HOLDING AS based?

POW HOLDING AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.