biztrac. BETA
COMPANY REGISTER PROFILE
983213197 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other activities of other membership organisations

GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND

Org. no. 983213197 Association/club/organisation (FLI) Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 179,000
Operating profit NOK −100,000
Equity NOK 825,000
Incorporated 1976

Signals

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

GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND is registered as a association/club/organisation with organisation number 983213197. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1976. The most recent filed accounts, for the 2025 financial year, show NOK 179,000 in revenue and NOK −100,000 in operating profit.

Key figures · 2025

Revenue
NOK 179,000
▲ +44 %
Operating profit
NOK −100,000
▼ −24 %
Equity
NOK 825,000
▼ −7 %
Est. value
NOK 540,000

Financial health · 2024

Liquidity
8.48
Very good
Current assets ÷ current liabilities
Profitability
-6.7%
Not satisfactory
Return on total assets
Solidity
88.2%
Very good
Equity as a share of total capital

Who owns GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND?

No shareholders are registered for GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND

What is the revenue of GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND?

GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND had revenue of NOK 179,000 in 2025.

Who is the general manager of GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND?

Tom Tidemann is registered as general manager of GJØVIK REVMATIKERFORENING NORSK REVMATIKERFORBUND.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.