BIZTRAC BETA
Rental and operating of own or leased real estate

EMSAKR AS

Org. no. 922349053 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 5.1m
Equity NOK 5.1m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-05 Adresseendring registrert 2026-02-05.

EMSAKR AS is registered as a limited company in Oslo, Oslo with organisation number 922349053. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 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 2024 financial year, show NOK 5.3m in revenue and NOK 5.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 5.1m
Equity
NOK 5.1m
Est. value
NOK 13.7m

Financial health · 2024

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

Who owns EMSAKR AS?

ADRIAN TOFTING
EMSAKR AS
NOK 5.3m rev. · NOK 5.1m profit

EMSAKR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EMSAKR AS own?

EMSAKR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EMSAKR AS

Who owns EMSAKR AS?

ADRIAN TOFTING is the largest registered owner, with 100.0%.

What is the revenue of EMSAKR AS?

EMSAKR AS had revenue of NOK 5.3m in 2024.

Where is EMSAKR AS based?

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