BIZTRAC BETA
Other education activities

LFS HOLDING AS

Org. no. 912219496 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −167,000
Equity NOK 12.8m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−167k kr).

LFS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 912219496. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte aksjer innen forlags- og skolevirksomhet, samt annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −167,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −167,000
Equity
NOK 12.8m
Est. value
NOK 15.7m

Financial health · 2024

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

Who owns LFS HOLDING AS?

THOR ALVIK
LFS HOLDING AS
NOK 0 rev. · NOK −167,000 profit

LFS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LFS HOLDING AS own?

LFS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LFS HOLDING AS

Who owns LFS HOLDING AS?

THOR ALVIK is the largest registered owner, with 100.0%.

What is the revenue of LFS HOLDING AS?

LFS HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of LFS HOLDING AS?

Thor Alvik is registered as general manager of LFS HOLDING AS.

Where is LFS HOLDING AS based?

LFS HOLDING AS has its business address in Oslo.

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.