biztrac. BETA
COMPANY REGISTER PROFILE
931073680 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of construction and civil engineering machinery and equipment

TRIVA DRIFT AS

Org. no. 931073680 Limited company (AS) Ullensaker Incorporated 2023 Active
Revenue 2025 NOK 6.1m
Operating profit NOK 436,000
Equity NOK 408,000
Incorporated 2023
Share capital NOK 100,000

TRIVA DRIFT AS is registered as a limited company in Ullensaker, Akershus with organisation number 931073680. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av maskiner og biler, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 436,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 436,000
▲ +1339 %
Equity
NOK 408,000
▲ +589 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
69.5%
Very good
Return on total assets
Solidity
34.5%
Good
Equity as a share of total capital

Who owns TRIVA DRIFT AS?

TRIVA DRIFT AS
NOK 6.1m rev. · NOK 436,000 profit

TRIVA DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIVA DRIFT AS

Who owns TRIVA DRIFT AS?

STITT HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TRIVA DRIFT AS?

TRIVA DRIFT AS had revenue of NOK 6.1m in 2025.

Who is the general manager of TRIVA DRIFT AS?

Truls Erik Ørpen is registered as general manager of TRIVA DRIFT AS.

Where is TRIVA DRIFT AS based?

TRIVA DRIFT AS has its business address in Jessheim.

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.