BIZTRAC BETA
Uoppgitt

EIGARSKAP AS

Org. no. 932171546 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 16,000
Incorporated 2023
Share capital NOK 36,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

EIGARSKAP AS is registered as a limited company in Bergen, Vestland with organisation number 932171546. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 36,000, divided into 36000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 16,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns EIGARSKAP AS?

ANDREAS HALLERAKER
EIGARSKAP AS
NOK 0 rev. · NOK −9,000 profit

EIGARSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIGARSKAP AS own?

EIGARSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIGARSKAP AS

Who owns EIGARSKAP AS?

ANDREAS HALLERAKER is the largest registered owner, with 100.0%.

What is the revenue of EIGARSKAP AS?

EIGARSKAP AS had revenue of NOK 0 in 2025.

Where is EIGARSKAP AS based?

EIGARSKAP 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.