BIZTRAC BETA
Intermediation service activities for real estate activities

NORD EIENDOMSMEGLING AS

Org. no. 929451422 Limited company (AS) Nordre Follo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 672,000
Equity NOK 500,000
Incorporated 2022
Employees 5
Share capital NOK 500,000

NORD EIENDOMSMEGLING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 929451422. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2022 and has 5 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eiendomsmegling.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 672,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 672,000
Equity
NOK 500,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns NORD EIENDOMSMEGLING AS?

NORDERHAUG HOLDING AS
NORD EIENDOMSMEGLING AS
NOK 7.5m rev. · NOK 672,000 profit

NORD EIENDOMSMEGLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORD EIENDOMSMEGLING AS

Who owns NORD EIENDOMSMEGLING AS?

NORDERHAUG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NORD EIENDOMSMEGLING AS?

NORD EIENDOMSMEGLING AS had revenue of NOK 7.5m in 2024.

Who is the general manager of NORD EIENDOMSMEGLING AS?

Bent André Norderhaug is registered as general manager of NORD EIENDOMSMEGLING AS.

Where is NORD EIENDOMSMEGLING AS based?

NORD EIENDOMSMEGLING AS has its business address in Oppegård.

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.