BIZTRAC BETA
Activities of fitness centres

FEELGOOD NESODDEN AS

Org. no. 931800566 Limited company (AS) Nesodden Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −52,000
Equity NOK −28,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−28k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−52k kr).

FEELGOOD NESODDEN AS is registered as a limited company in Nesodden, Akershus with organisation number 931800566. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av treningssenter innenfor Feelgood treningskonsept samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −52,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −52,000
Equity
NOK −28,000

Financial health · 2024

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

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

Who owns FEELGOOD NESODDEN AS?

OLSEN HOLDING NESODDEN AS
FEELGOOD NESODDEN AS
NOK 1.4m rev. · NOK −52,000 profit

FEELGOOD NESODDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FEELGOOD NESODDEN AS

Who owns FEELGOOD NESODDEN AS?

OLSEN HOLDING NESODDEN AS is the largest registered owner, with 100.0%.

What is the revenue of FEELGOOD NESODDEN AS?

FEELGOOD NESODDEN AS had revenue of NOK 1.4m in 2024.

Where is FEELGOOD NESODDEN AS based?

FEELGOOD NESODDEN AS has its business address in Nesoddtangen.

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.