BIZTRAC BETA
Other health services

FABSER HELSE AS

Org. no. 923830421 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK −12,000
Equity NOK 774,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

FABSER HELSE AS is registered as a limited company in Oslo, Oslo with organisation number 923830421. The business is classified under other health services (NACE 86.993). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Helsetjenester innen nerve, muskler og skjelett.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK −12,000
Equity
NOK 774,000
Est. value
NOK 4.9m

Financial health · 2024

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.4%
Good
Equity as a share of total capital

Who owns FABSER HELSE AS?

SERINE ARNY SKARPSNO-LALIM
FABSER HELSE AS
NOK 5.6m rev. · NOK −12,000 profit

FABSER HELSE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FABSER HELSE AS own?

FABSER HELSE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FABSER HELSE AS

Who owns FABSER HELSE AS?

SERINE ARNY SKARPSNO-LALIM is the largest registered owner, with 50.0%.

What is the revenue of FABSER HELSE AS?

FABSER HELSE AS had revenue of NOK 5.6m in 2024.

Who is the general manager of FABSER HELSE AS?

Fabian Skarpsno-Lalim is registered as general manager of FABSER HELSE AS.

Where is FABSER HELSE AS based?

FABSER HELSE 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.