BIZTRAC BETA
Buying and selling of own real estate

AMBOLT EIENDOM AS

Org. no. 923060537 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK 517,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

AMBOLT EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 923060537. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 517,000
Est. value
NOK 472,000

Financial health · 2024

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

Who owns AMBOLT EIENDOM AS?

ALEXANDER NÆSS ALMELAND
AMBOLT EIENDOM AS
NOK 0 rev. · NOK −23,000 profit

AMBOLT EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AMBOLT EIENDOM AS own?

AMBOLT EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AMBOLT EIENDOM AS

Who owns AMBOLT EIENDOM AS?

ALEXANDER NÆSS ALMELAND is the largest registered owner, with 50.0%.

What is the revenue of AMBOLT EIENDOM AS?

AMBOLT EIENDOM AS had revenue of NOK 0 in 2024.

Where is AMBOLT EIENDOM AS based?

AMBOLT EIENDOM AS has its business address in Oslo.

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.