BIZTRAC BETA
Rental and operating of own or leased real estate

OORD EIENDOM AS

Org. no. 970897364 Limited company (AS) Ullensaker Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 22.8m
Operating profit NOK 12.7m
Equity NOK 61.8m
Incorporated 1994
Share capital NOK 950,000

OORD EIENDOM AS is registered as a limited company in Ullensaker, Akershus with organisation number 970897364. 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 950,000. The company's stated purpose is: “Import, handel, verksteddrift, eiendomsvirksomhet og enhver virksomhet som er i forbindelse dermed, anbringelse av selskapets midler i andre selskaper eller ved investering på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.8m in revenue and NOK 12.7m in operating profit.

Key figures · 2024

Revenue
NOK 22.8m
Operating profit
NOK 12.7m
Equity
NOK 61.8m
Est. value
NOK 66.2m

Financial health · 2024

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

Who owns OORD EIENDOM AS?

OORD HOLDING AS
OORD EIENDOM AS
NOK 22.8m rev. · NOK 12.7m profit

OORD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OORD EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about OORD EIENDOM AS

Who owns OORD EIENDOM AS?

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

What is the revenue of OORD EIENDOM AS?

OORD EIENDOM AS had revenue of NOK 22.8m in 2024.

Who is the general manager of OORD EIENDOM AS?

Paul Oord is registered as general manager of OORD EIENDOM AS.

Where is OORD EIENDOM AS based?

OORD EIENDOM AS has its business address in Jessheim.

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.