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

VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13

Org. no. 923109684 Association/club/organisation (FLI) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 177,000
Operating profit NOK 68,000
Equity NOK 68,000
Incorporated 2019

Signals

1 flags
  • Nylig endring 2026-08-26 Adresseendring registrert 2026-08-26.

VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13 is registered as a association/club/organisation in Stavanger, Rogaland with organisation number 923109684. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2019. The most recent filed accounts, for the 2025 financial year, show NOK 177,000 in revenue and NOK 68,000 in operating profit.

Key figures · 2025

Revenue
NOK 177,000
Operating profit
NOK 68,000
Equity
NOK 68,000
Est. value
NOK 247,000

Financial health · 2025

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

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

Who owns VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13?

No shareholders are registered for VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13

What is the revenue of VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13?

VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13 had revenue of NOK 177,000 in 2025.

Where is VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13 based?

VELFORENINGEN SANDANGERSVINGEN TUN 7 - TUN 13 has its business address in Stavanger.

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.