BIZTRAC BETA
Other real estate activities on a fee or contract basis

AREALPARTNER NÆRINGSMEGLING AS

Org. no. 913107683 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 10.4m
Operating profit NOK −55,000
Equity NOK 946,000
Incorporated 2014
Share capital NOK 100,000

Signals

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

AREALPARTNER NÆRINGSMEGLING AS is registered as a limited company in Oslo, Oslo with organisation number 913107683. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Formidling av fast eiendom/eiendomsmegling, samt alt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.4m in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.4m
Operating profit
NOK −55,000
Equity
NOK 946,000
Est. value
NOK 16.2m

Financial health · 2025

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

Who owns AREALPARTNER NÆRINGSMEGLING AS?

SILJE CAROLINE BOLSTAD
AREALPARTNER NÆRINGSMEGLING AS
NOK 10.4m rev. · NOK −55,000 profit

AREALPARTNER NÆRINGSMEGLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AREALPARTNER NÆRINGSMEGLING AS

Who owns AREALPARTNER NÆRINGSMEGLING AS?

SILJE CAROLINE BOLSTAD is the largest registered owner, with 50.0%.

What is the revenue of AREALPARTNER NÆRINGSMEGLING AS?

AREALPARTNER NÆRINGSMEGLING AS had revenue of NOK 10.4m in 2025.

Where is AREALPARTNER NÆRINGSMEGLING AS based?

AREALPARTNER NÆRINGSMEGLING 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.