BIZTRAC BETA
Other health services

FRISKGÅRDEN NAMDAL AS

Org. no. 984781121 Limited company (AS) Grong Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 209,000
Operating profit NOK −865,000
Equity NOK 2.5m
Incorporated 2002
Share capital NOK 680,000

Signals

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

FRISKGÅRDEN NAMDAL AS is registered as a limited company in Grong, Trøndelag with organisation number 984781121. The business is classified under other health services (NACE 86.993). The company was incorporated in 2002. Registered share capital is NOK 680,000, divided into 680 shares. The company's stated purpose is: “Drive lokal Friskgård i Namdalen med organisering og salg av helsetjenester i form av lærings- og mestringsprogram, tilby HMS-tjenester til offentlige og private virksomheter samt øvrig virksomhet som naturlig står i forbindelse med disse hovedvirksomhetene.”. The most recent filed accounts, for the 2024 financial year, show NOK 209,000 in revenue and NOK −865,000 in operating profit.

Key figures · 2024

Revenue
NOK 209,000
Operating profit
NOK −865,000
Equity
NOK 2.5m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns FRISKGÅRDEN NAMDAL AS?

FRISKGÅRDEN AS
FRISKGÅRDEN NAMDAL AS
NOK 209,000 rev. · NOK −865,000 profit

FRISKGÅRDEN NAMDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRISKGÅRDEN NAMDAL AS

Who owns FRISKGÅRDEN NAMDAL AS?

FRISKGÅRDEN AS is the largest registered owner, with 100.0%.

What is the revenue of FRISKGÅRDEN NAMDAL AS?

FRISKGÅRDEN NAMDAL AS had revenue of NOK 209,000 in 2024.

Where is FRISKGÅRDEN NAMDAL AS based?

FRISKGÅRDEN NAMDAL AS has its business address in Grong.

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.