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

STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND

Org. no. 997864646 Association/club/organisation (FLI) Bergen Incorporated 2011 Active
Revenue 2025 NOK 372,000
Operating profit NOK −36,000
Equity NOK 443,000
Incorporated 2011

Signals

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

STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND is registered as a association/club/organisation in Bergen, Vestland with organisation number 997864646. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2011. The most recent filed accounts, for the 2025 financial year, show NOK 372,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 372,000
▼ −41 %
Operating profit
NOK −36,000
▼ −106 %
Equity
NOK 443,000
Est. value
NOK 824,000

Financial health · 2019

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

Who owns STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND?

No shareholders are registered for STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND

What is the revenue of STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND?

STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND had revenue of NOK 372,000 in 2025.

Where is STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND based?

STØTTEGRUPPEN FOR BERØRTE ETTER 22. JULI I HORDALAND has its business address in Bergen.

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.