BIZTRAC BETA
Rental and operating of own or leased real estate

LFI HELSE & TRENING AS

Org. no. 984660472 Limited company (AS) Lillestrøm Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 1.3m
Equity NOK 4.2m
Incorporated 2002
Share capital NOK 157,000

LFI HELSE & TRENING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 984660472. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 157,000, divided into 252 shares. The company's stated purpose is: “Fremleie av lokaler og driftsmidler, administrasjon og fordeling av kostnader til leietakere innen fysioterapi og andre helsetjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 1.3m
Equity
NOK 4.2m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns LFI HELSE & TRENING AS?

FRODE KRISTIANSEN
LFI HELSE & TRENING AS
NOK 8.2m rev. · NOK 1.3m profit

LFI HELSE & TRENING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about LFI HELSE & TRENING AS

Who owns LFI HELSE & TRENING AS?

FRODE KRISTIANSEN is the largest registered owner, with 16.7%.

What is the revenue of LFI HELSE & TRENING AS?

LFI HELSE & TRENING AS had revenue of NOK 8.2m in 2024.

Who is the general manager of LFI HELSE & TRENING AS?

Thomas Sewell is registered as general manager of LFI HELSE & TRENING AS.

Where is LFI HELSE & TRENING AS based?

LFI HELSE & TRENING AS has its business address in Lillestrøm.

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.