BIZTRAC BETA
Rental and operating of own or leased real estate

MORDI EIENDOM AS

Org. no. 990223998 Limited company (AS) Bamble Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 396,000
Operating profit NOK 141,000
Equity NOK −1.7m
Incorporated 2006
Share capital NOK 450,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,7 mill kr).

MORDI EIENDOM AS is registered as a limited company in Bamble, Telemark with organisation number 990223998. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 450,000, divided into 4500 shares. The company's stated purpose is: “Kjøp,salg og utleie av fast eiendom samt eie og bestyre aksjer og eierparter i andre selskap og det som naturlig knytter seg til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 396,000 in revenue and NOK 141,000 in operating profit.

Key figures · 2025

Revenue
NOK 396,000
Operating profit
NOK 141,000
Equity
NOK −1.7m
Est. value
NOK 849,000

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-86.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MORDI EIENDOM AS?

VICTORIA EIENDOM OG HOTELL AS
MORDI EIENDOM AS
NOK 396,000 rev. · NOK 141,000 profit

MORDI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MORDI EIENDOM AS

Who owns MORDI EIENDOM AS?

VICTORIA EIENDOM OG HOTELL AS is the largest registered owner, with 100.0%.

What is the revenue of MORDI EIENDOM AS?

MORDI EIENDOM AS had revenue of NOK 396,000 in 2025.

Where is MORDI EIENDOM AS based?

MORDI EIENDOM AS has its business address in Langesund.

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.