BIZTRAC BETA
COMPANY REGISTER PROFILE
931673327 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

MOLIND EIENDOM AS

Org. no. 931673327 Limited company (AS) Ringerike Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 584,000
Equity NOK 3.3m
Incorporated 2023
Share capital NOK 1.0m

MOLIND EIENDOM AS is registered as a limited company in Ringerike, Buskerud with organisation number 931673327. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Eie og drive fast eiendom, investeringer i andre selskaper, investeringer i aksjer og andre verdipapirer og det som derved er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 584,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 584,000
Equity
NOK 3.3m
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
5.55
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns MOLIND EIENDOM AS?

MOLIND EIENDOM AS
NOK 1.0m rev. · NOK 584,000 profit

MOLIND EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOLIND EIENDOM AS

Who owns MOLIND EIENDOM AS?

MOLIND HOLDING AS is the largest registered owner, with 91.0%.

What is the revenue of MOLIND EIENDOM AS?

MOLIND EIENDOM AS had revenue of NOK 1.0m in 2025.

Who is the general manager of MOLIND EIENDOM AS?

Morten Øverby is registered as general manager of MOLIND EIENDOM AS.

Where is MOLIND EIENDOM AS based?

MOLIND EIENDOM AS has its business address in Hønefoss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.