BIZTRAC BETA
Intermediation service activities for real estate activities

LOFOTEN EIENDOMSMEGLING AS

Org. no. 998643058 Limited company (AS) Vågan Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 149,000
Equity NOK 614,000
Incorporated 2012
Share capital NOK 200,000

LOFOTEN EIENDOMSMEGLING AS is registered as a limited company in Vågan, Nordland with organisation number 998643058. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2012. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Drive eiendomsmegling i samsvar med eiendomsmeglingsloven § 5-1 (1).”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 149,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 149,000
Equity
NOK 614,000
Est. value
NOK 787,000

Financial health · 2024

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

Who owns LOFOTEN EIENDOMSMEGLING AS?

STIAN ENGSTAD FREDRIKSEN
LOFOTEN EIENDOMSMEGLING AS
NOK 3.7m rev. · NOK 149,000 profit

LOFOTEN EIENDOMSMEGLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOFOTEN EIENDOMSMEGLING AS

Who owns LOFOTEN EIENDOMSMEGLING AS?

STIAN ENGSTAD FREDRIKSEN is the largest registered owner, with 50.0%.

What is the revenue of LOFOTEN EIENDOMSMEGLING AS?

LOFOTEN EIENDOMSMEGLING AS had revenue of NOK 3.7m in 2024.

Who is the general manager of LOFOTEN EIENDOMSMEGLING AS?

Jonas Emilsen is registered as general manager of LOFOTEN EIENDOMSMEGLING AS.

Where is LOFOTEN EIENDOMSMEGLING AS based?

LOFOTEN EIENDOMSMEGLING AS has its business address in Svolvær.

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.