BIZTRAC BETA
Rental and operating of own or leased real estate

APROPOS EIENDOM AS

Org. no. 871510652 Limited company (AS) Oslo Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 780,000
Operating profit NOK −759,000
Equity NOK 752,000
Incorporated 1994
Share capital NOK 1.0m

Signals

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

APROPOS EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 871510652. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 1.0m, divided into 1 shares. The company's stated purpose is: “Å eie, kjøpe, selge og drive fast eiendom og alt som dermed står i forbindelse, derunder som byggherre å delta i oppføring av nybygg. Selskapet kan gjøre seg interessert i andre selskaper ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 780,000 in revenue and NOK −759,000 in operating profit.

Key figures · 2025

Revenue
NOK 780,000
Operating profit
NOK −759,000
Equity
NOK 752,000
Est. value
NOK 687,000

Financial health · 2025

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

Who owns APROPOS EIENDOM AS?

K A ENQVIST ANS
APROPOS EIENDOM AS
NOK 780,000 rev. · NOK −759,000 profit

APROPOS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about APROPOS EIENDOM AS

Who owns APROPOS EIENDOM AS?

K A ENQVIST ANS is the largest registered owner, with 100.0%.

What is the revenue of APROPOS EIENDOM AS?

APROPOS EIENDOM AS had revenue of NOK 780,000 in 2025.

Where is APROPOS EIENDOM AS based?

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