BIZTRAC BETA
Physiotherapy activities

GRIMSTAD KLINIKKEN AS

Org. no. 858366712 Limited company (AS) Grimstad Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 814,000
Operating profit NOK −87,000
Equity NOK 237,000
Incorporated 1990
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−87k kr).

GRIMSTAD KLINIKKEN AS is registered as a limited company in Grimstad, Agder with organisation number 858366712. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 1990. Registered share capital is NOK 200,000, divided into 20 shares. The company's stated purpose is: “Fysikalsk virksomhet samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 814,000 in revenue and NOK −87,000 in operating profit.

Key figures · 2025

Revenue
NOK 814,000
Operating profit
NOK −87,000
Equity
NOK 237,000
Est. value
NOK 806,000

Financial health · 2025

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

Who owns GRIMSTAD KLINIKKEN AS?

RICHARD FARSUND
GRIMSTAD KLINIKKEN AS
NOK 814,000 rev. · NOK −87,000 profit

GRIMSTAD KLINIKKEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRIMSTAD KLINIKKEN AS

Who owns GRIMSTAD KLINIKKEN AS?

RICHARD FARSUND is the largest registered owner, with 25.0%.

What is the revenue of GRIMSTAD KLINIKKEN AS?

GRIMSTAD KLINIKKEN AS had revenue of NOK 814,000 in 2025.

Who is the general manager of GRIMSTAD KLINIKKEN AS?

Anne-Charlotte Fosse Haug is registered as general manager of GRIMSTAD KLINIKKEN AS.

Where is GRIMSTAD KLINIKKEN AS based?

GRIMSTAD KLINIKKEN AS has its business address in Grimstad.

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.