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

LUMIC EIENDOM II AS

Org. no. 997713672 Limited company (AS) Tysnes Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 157,000
Operating profit NOK 106,000
Equity NOK 141,000
Incorporated 2011
Share capital NOK 115,000

LUMIC EIENDOM II AS is registered as a limited company in Tysnes, Vestland with organisation number 997713672. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 115,000, divided into 100 shares. The company's stated purpose is: “Eie, å drive og å leie ut fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 157,000 in revenue and NOK 106,000 in operating profit.

Key figures · 2025

Revenue
NOK 157,000
▲ +1 %
Operating profit
NOK 106,000
▲ +21 %
Equity
NOK 141,000
▲ +138 %
Est. value
NOK 318,000

Financial health · 2025

Liquidity
2.81
Very good
Current assets ÷ current liabilities
Profitability
61.4%
Very good
Return on total assets
Solidity
80.7%
Very good
Equity as a share of total capital

Who owns LUMIC EIENDOM II AS?

LUMIC EIENDOM II AS
NOK 157,000 rev. · NOK 106,000 profit

LUMIC EIENDOM II AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUMIC EIENDOM II AS

Who owns LUMIC EIENDOM II AS?

R HAGEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of LUMIC EIENDOM II AS?

LUMIC EIENDOM II AS had revenue of NOK 157,000 in 2025.

Who is the general manager of LUMIC EIENDOM II AS?

Ronny Hagen is registered as general manager of LUMIC EIENDOM II AS.

Where is LUMIC EIENDOM II AS based?

LUMIC EIENDOM II AS has its business address in Lundegrend.

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.