BIZTRAC BETA
Operation of car parks and garages

OTTA BRYGGE P-HUS AS

Org. no. 915067166 Limited company (AS) Sel Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 268,000
Operating profit NOK 166,000
Equity NOK 193,000
Incorporated 2015
Share capital NOK 30,000

OTTA BRYGGE P-HUS AS is registered as a limited company in Sel, Innlandet with organisation number 915067166. The business is classified under operation of car parks and garages (NACE 52.212). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring, drift av parkeringshus, herunder kjøp og salg av parkeringsplasser. Selskapet kan i tillegg ved aksjetegning eller på annen måte investere i andre selskaper innenfor samme bransje.”. The most recent filed accounts, for the 2024 financial year, show NOK 268,000 in revenue and NOK 166,000 in operating profit.

Key figures · 2024

Revenue
NOK 268,000
Operating profit
NOK 166,000
Equity
NOK 193,000
Est. value
NOK 524,000

Financial health · 2024

Liquidity
0.50
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.4%
Satisfactory
Equity as a share of total capital

Who owns OTTA BRYGGE P-HUS AS?

STORSVINGEN AS
OTTA BRYGGE P-HUS AS
NOK 268,000 rev. · NOK 166,000 profit

OTTA BRYGGE P-HUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OTTA BRYGGE P-HUS AS

Who owns OTTA BRYGGE P-HUS AS?

STORSVINGEN AS is the largest registered owner, with 100.0%.

What is the revenue of OTTA BRYGGE P-HUS AS?

OTTA BRYGGE P-HUS AS had revenue of NOK 268,000 in 2024.

Who is the general manager of OTTA BRYGGE P-HUS AS?

Helge Ingar Barkenæs is registered as general manager of OTTA BRYGGE P-HUS AS.

Where is OTTA BRYGGE P-HUS AS based?

OTTA BRYGGE P-HUS AS has its business address in Nedre Heidal.

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.