BIZTRAC BETA
Rental and operating of own or leased real estate

AKIMI ASKER AS

Org. no. 995082802 Limited company (AS) Asker Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK −58,000
Equity NOK 222,000
Incorporated 2010
Share capital NOK 825,000

Signals

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

AKIMI ASKER AS is registered as a limited company in Asker, Akershus with organisation number 995082802. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 825,000, divided into 8250 shares. The company's stated purpose is: “Utleie av lokaler og utstyr for fysikalsk tjenesteyting og virksomhet i forbindelse med dette. Det vil også være salgsvirksomhet knyttet til driften. ”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK −58,000
Equity
NOK 222,000
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns AKIMI ASKER AS?

HANS CHRISTIAN LØWØ
AKIMI ASKER AS
NOK 4.8m rev. · NOK −58,000 profit

AKIMI ASKER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKIMI ASKER AS

Who owns AKIMI ASKER AS?

HANS CHRISTIAN LØWØ is the largest registered owner, with 78.1%.

What is the revenue of AKIMI ASKER AS?

AKIMI ASKER AS had revenue of NOK 4.8m in 2024.

Who is the general manager of AKIMI ASKER AS?

Hans Christian Løwø is registered as general manager of AKIMI ASKER AS.

Where is AKIMI ASKER AS based?

AKIMI ASKER AS has its business address in Asker.

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.