BIZTRAC BETA
Rental and operating of own or leased real estate

ARMA EIENDOM AS

Org. no. 988827584 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 1.5m
Equity NOK 2.9m
Incorporated 2005
Share capital NOK 2.9m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ARMA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 988827584. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.9m, divided into 2870 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 1.5m
Equity
NOK 2.9m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns ARMA EIENDOM AS?

ATLAS DAGLIGVARE 3 AS
ARMA EIENDOM AS
NOK 2.5m rev. · NOK 1.5m profit

ARMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARMA EIENDOM AS own?

ARMA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARMA EIENDOM AS

Who owns ARMA EIENDOM AS?

ATLAS DAGLIGVARE 3 AS is the largest registered owner, with 100.0%.

What is the revenue of ARMA EIENDOM AS?

ARMA EIENDOM AS had revenue of NOK 2.5m in 2025.

Where is ARMA EIENDOM AS based?

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