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

TROMS BARNE- OG UNGDOMSRÅD (TROBUR)

Org. no. 979994354 Association/club/organisation (FLI) Tromsø Incorporated 1998 Active
Ownership graph ↗
Revenue 2022 NOK 2.0m
Operating profit NOK −33,000
Equity NOK 420,000
Incorporated 1998

Signals

1 flags
  • Driftsunderskudd 2022 Siste driftsresultat er negativt (−33k kr).

TROMS BARNE- OG UNGDOMSRÅD (TROBUR) is registered as a association/club/organisation in Tromsø, Troms with organisation number 979994354. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1998. The most recent filed accounts, for the 2022 financial year, show NOK 2.0m in revenue and NOK −33,000 in operating profit.

Key figures · 2022

Revenue
NOK 2.0m
▼ −2 %
Operating profit
NOK −33,000
▼ −128 %
Equity
NOK 420,000
▼ −7 %
Est. value
NOK 438,000

Financial health · 2022

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

Who owns TROMS BARNE- OG UNGDOMSRÅD (TROBUR)?

No shareholders are registered for TROMS BARNE- OG UNGDOMSRÅD (TROBUR) in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TROMS BARNE- OG UNGDOMSRÅD (TROBUR)

What is the revenue of TROMS BARNE- OG UNGDOMSRÅD (TROBUR)?

TROMS BARNE- OG UNGDOMSRÅD (TROBUR) had revenue of NOK 2.0m in 2022.

Who is the general manager of TROMS BARNE- OG UNGDOMSRÅD (TROBUR)?

Silje Haukland Ryvold is registered as general manager of TROMS BARNE- OG UNGDOMSRÅD (TROBUR).

Where is TROMS BARNE- OG UNGDOMSRÅD (TROBUR) based?

TROMS BARNE- OG UNGDOMSRÅD (TROBUR) has its business address in Tromsø.

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.