BIZTRAC BETA
Rental and operating of own or leased real estate

PÅL BRÅTHEN HOLDING AS

Org. no. 917032556 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 22,000
Operating profit NOK 10,000
Equity NOK 4,000
Incorporated 2016
Share capital NOK 30,000

PÅL BRÅTHEN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 917032556. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, investering i fast eiendom og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 22,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 22,000
Operating profit
NOK 10,000
Equity
NOK 4,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns PÅL BRÅTHEN HOLDING AS?

PÅL TANGEN BRÅTHEN
PÅL BRÅTHEN HOLDING AS
NOK 22,000 rev. · NOK 10,000 profit

PÅL BRÅTHEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PÅL BRÅTHEN HOLDING AS own?

PÅL BRÅTHEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PÅL BRÅTHEN HOLDING AS

Who owns PÅL BRÅTHEN HOLDING AS?

PÅL TANGEN BRÅTHEN is the largest registered owner, with 100.0%.

What is the revenue of PÅL BRÅTHEN HOLDING AS?

PÅL BRÅTHEN HOLDING AS had revenue of NOK 22,000 in 2025.

Where is PÅL BRÅTHEN HOLDING AS based?

PÅL BRÅTHEN HOLDING AS has its business address in Bergen.

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.