BIZTRAC BETA
Rental and operating of own or leased real estate

MIDT-LOFOTEN EIENDOM AS

Org. no. 915303560 Limited company (AS) Vestvågøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 911,000
Operating profit NOK 305,000
Equity NOK 30,000
Incorporated 2015
Share capital NOK 30,000

MIDT-LOFOTEN EIENDOM AS is registered as a limited company in Vestvågøy, Nordland with organisation number 915303560. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Kjøp/salg/utleie av egen eller leid fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 911,000 in revenue and NOK 305,000 in operating profit.

Key figures · 2024

Revenue
NOK 911,000
Operating profit
NOK 305,000
Equity
NOK 30,000
Est. value
NOK 607,000

Financial health · 2024

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

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

Who owns MIDT-LOFOTEN EIENDOM AS?

LOFOTR HOLDING AS
MIDT-LOFOTEN EIENDOM AS
NOK 911,000 rev. · NOK 305,000 profit

MIDT-LOFOTEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDT-LOFOTEN EIENDOM AS

Who owns MIDT-LOFOTEN EIENDOM AS?

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

What is the revenue of MIDT-LOFOTEN EIENDOM AS?

MIDT-LOFOTEN EIENDOM AS had revenue of NOK 911,000 in 2024.

Who is the general manager of MIDT-LOFOTEN EIENDOM AS?

Ole Vegard Mosseng is registered as general manager of MIDT-LOFOTEN EIENDOM AS.

Where is MIDT-LOFOTEN EIENDOM AS based?

MIDT-LOFOTEN EIENDOM AS has its business address in Leknes.

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.