BIZTRAC BETA
Activities of fitness centres

FLEX NENSET AS

Org. no. 923992103 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −12,000
Equity NOK 72,000
Incorporated 2019
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).
  • Nylig endring 2026-05-19 Adresseendring registrert 2026-05-19.

FLEX NENSET AS is registered as a limited company in Skien, Telemark with organisation number 923992103. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drift av treningssenter og annet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −12,000
Equity
NOK 72,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.1%
Weak
Equity as a share of total capital

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

Who owns FLEX NENSET AS?

FLEX-HOLDING AS
FLEX NENSET AS
NOK 1.2m rev. · NOK −12,000 profit

FLEX NENSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLEX NENSET AS

Who owns FLEX NENSET AS?

FLEX-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FLEX NENSET AS?

FLEX NENSET AS had revenue of NOK 1.2m in 2025.

Who is the general manager of FLEX NENSET AS?

Ronny Rakland is registered as general manager of FLEX NENSET AS.

Where is FLEX NENSET AS based?

FLEX NENSET AS has its business address in Skien.

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.