BIZTRAC BETA
Rental and operating of own or leased real estate

NORGESFERIE AS

Org. no. 981515897 Limited company (AS) Lindesnes Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 57,000
Equity NOK 535,000
Incorporated 2000
Employees 5
Share capital NOK 2.0m

NORGESFERIE AS is registered as a limited company in Lindesnes, Agder with organisation number 981515897. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000 and has 5 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Utleie, kjøp og salg av fast eiendom, handel og alt hva hermed som står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 57,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 57,000
Equity
NOK 535,000
Est. value
NOK 531,000

Financial health · 2024

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.7%
Very good
Equity as a share of total capital

Who owns NORGESFERIE AS?

MAGNUS MIDLING-JENSSEN
NORGESFERIE AS
NOK 4.3m rev. · NOK 57,000 profit

NORGESFERIE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORGESFERIE AS

Who owns NORGESFERIE AS?

MAGNUS MIDLING-JENSSEN is the largest registered owner, with 52.0%.

What is the revenue of NORGESFERIE AS?

NORGESFERIE AS had revenue of NOK 4.3m in 2024.

Who is the general manager of NORGESFERIE AS?

Magnus Midling-Jenssen is registered as general manager of NORGESFERIE AS.

Where is NORGESFERIE AS based?

NORGESFERIE AS has its business address in Lindesnes.

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.