biztrac. BETA
COMPANY REGISTER PROFILE
921803524 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

TOTRI CONSULT AS

Org. no. 921803524 Limited company (AS) Hol Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 672,000
Operating profit NOK 84,000
Equity NOK 249,000
Incorporated 2018
Share capital NOK 30,000

TOTRI CONSULT AS is registered as a limited company in Hol, Buskerud with organisation number 921803524. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive med rådgivning innen skiidrett og annen idrett, samt yte tilknyttet tjenester innen salg, forvaltning og administrasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 672,000 in revenue and NOK 84,000 in operating profit.

Key figures · 2025

Revenue
NOK 672,000
▲ +54 %
Operating profit
NOK 84,000
▲ +262 %
Equity
NOK 249,000
▲ +34 %
Est. value
NOK 499,000

Financial health · 2025

Liquidity
8.16
Very good
Current assets ÷ current liabilities
Profitability
34.4%
Very good
Return on total assets
Solidity
87.7%
Very good
Equity as a share of total capital

Who owns TOTRI CONSULT AS?

TOTRI CONSULT AS
NOK 672,000 rev. · NOK 84,000 profit

TOTRI CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOTRI CONSULT AS

Who owns TOTRI CONSULT AS?

Trine Dyveke Tviberg is the largest registered owner, with 100.0%.

What is the revenue of TOTRI CONSULT AS?

TOTRI CONSULT AS had revenue of NOK 672,000 in 2025.

Who is the general manager of TOTRI CONSULT AS?

Trine Dyveke Tviberg is registered as general manager of TOTRI CONSULT AS.

Where is TOTRI CONSULT AS based?

TOTRI CONSULT AS has its business address in Geilo.

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.