BIZTRAC BETA
Site preparation

BRTH HOLDING AS

Org. no. 934323602 Limited company (AS) Alta Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
Share capital NOK 120,000

BRTH HOLDING AS is registered as a limited company in Alta, Finnmark with organisation number 934323602. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 120,000, divided into 60 shares. The company's stated purpose is: “Investere i selskaper, verdipapirfond, eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer og andre finansielle instrumenter, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 31,000

Financial health · 2024

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

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

Who owns BRTH HOLDING AS?

FILIP THOMASSEN
BRTH HOLDING AS
NOK 0 rev. · NOK 0 profit

BRTH HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRTH HOLDING AS own?

BRTH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRTH HOLDING AS

Who owns BRTH HOLDING AS?

FILIP THOMASSEN is the largest registered owner, with 50.0%.

What is the revenue of BRTH HOLDING AS?

BRTH HOLDING AS had revenue of NOK 0 in 2024.

Where is BRTH HOLDING AS based?

BRTH HOLDING AS has its business address in Alta.

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.