BIZTRAC BETA
Other health services

FRISKLIVSHELSE AS

Org. no. 932421852 Limited company (AS) Vennesla Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 218,000
Operating profit NOK −26,000
Equity NOK −1,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

FRISKLIVSHELSE AS is registered as a limited company in Vennesla, Agder with organisation number 932421852. The business is classified under other health services (NACE 86.993). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Helse- og frisklivscoaching - medisinsk veiledning.”. The most recent filed accounts, for the 2025 financial year, show NOK 218,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 218,000
Operating profit
NOK −26,000
Equity
NOK −1,000

Financial health · 2025

Liquidity
-41.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.0%
Weak
Equity as a share of total capital

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

Who owns FRISKLIVSHELSE AS?

MARIANNE NILSEN
FRISKLIVSHELSE AS
NOK 218,000 rev. · NOK −26,000 profit

FRISKLIVSHELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRISKLIVSHELSE AS

Who owns FRISKLIVSHELSE AS?

MARIANNE NILSEN is the largest registered owner, with 100.0%.

What is the revenue of FRISKLIVSHELSE AS?

FRISKLIVSHELSE AS had revenue of NOK 218,000 in 2025.

Who is the general manager of FRISKLIVSHELSE AS?

Marianne Nilsen is registered as general manager of FRISKLIVSHELSE AS.

Where is FRISKLIVSHELSE AS based?

FRISKLIVSHELSE AS has its business address in Vennesla.

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.