BIZTRAC BETA
Rental and operating of own or leased real estate

LEIF FOSSUM EIENDOM AS

Org. no. 933668061 Limited company (AS) Midt-Telemark Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 180,000
Operating profit NOK 38,000
Equity NOK 2.9m
Incorporated 1982
Share capital NOK 150,000

LEIF FOSSUM EIENDOM AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 933668061. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 150,000, divided into 50 shares. The company's stated purpose is: “Eiendomsutvikling herunder kjøp, salg og utleie av fast eiendom og hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 180,000 in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 180,000
Operating profit
NOK 38,000
Equity
NOK 2.9m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns LEIF FOSSUM EIENDOM AS?

LEIF TORSTEIN FOSSUM
LEIF FOSSUM EIENDOM AS
NOK 180,000 rev. · NOK 38,000 profit

LEIF FOSSUM EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEIF FOSSUM EIENDOM AS

Who owns LEIF FOSSUM EIENDOM AS?

LEIF TORSTEIN FOSSUM is the largest registered owner, with 36.0%.

What is the revenue of LEIF FOSSUM EIENDOM AS?

LEIF FOSSUM EIENDOM AS had revenue of NOK 180,000 in 2025.

Who is the general manager of LEIF FOSSUM EIENDOM AS?

Leif Torstein Fossum is registered as general manager of LEIF FOSSUM EIENDOM AS.

Where is LEIF FOSSUM EIENDOM AS based?

LEIF FOSSUM EIENDOM AS has its business address in Gvarv.

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.