biztrac. BETA
COMPANY REGISTER PROFILE
994306839 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

L&F EIENDOM AS

Org. no. 994306839 Limited company (AS) Hjartdal Incorporated 2009 Active
Revenue 2025 NOK 14.1m
Operating profit NOK −2.8m
Equity NOK −998,000
Incorporated 2009
Share capital NOK 2.5m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−998k kr).

L&F EIENDOM AS is registered as a limited company in Hjartdal, Telemark with organisation number 994306839. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 2.5m, divided into 25000 shares. The company's stated purpose is: “Utvikling av høykvalitets fritidseiendommer for salg og utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.1m in revenue and NOK −2.8m in operating profit.

Key figures · 2025

Revenue
NOK 14.1m
Operating profit
NOK −2.8m
▼ −199 %
Equity
NOK −998,000
▼ −155 %

Financial health · 2025

Liquidity
86.04
Very good
Current assets ÷ current liabilities
Profitability
-24.7%
Not satisfactory
Return on total assets
Solidity
-26.3%
Weak
Equity as a share of total capital

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

Who owns L&F EIENDOM AS?

L&F EIENDOM AS
NOK 14.1m rev. · NOK −2.8m profit

L&F EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about L&F EIENDOM AS

Who owns L&F EIENDOM AS?

Erik Flingtorp is the largest registered owner, with 68.0%.

What is the revenue of L&F EIENDOM AS?

L&F EIENDOM AS had revenue of NOK 14.1m in 2025.

Who is the general manager of L&F EIENDOM AS?

Erik Flingtorp is registered as general manager of L&F EIENDOM AS.

Where is L&F EIENDOM AS based?

L&F EIENDOM AS has its business address in Sauland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.