BIZTRAC BETA
Retail sale of automotive fuel

TORKEL SCHIVE AS

Org. no. 988294454 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 80.5m
Operating profit NOK 782,000
Equity NOK 2.0m
Incorporated 2005
Employees 93
Share capital NOK 900,000

TORKEL SCHIVE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988294454. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2005 and has 93 registered employees. Registered share capital is NOK 900,000, divided into 100 shares. The company's stated purpose is: “Drift av bensinstasjon, varehandel, matservering samt hva dertil står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 80.5m in revenue and NOK 782,000 in operating profit.

Key figures · 2025

Revenue
NOK 80.5m
Operating profit
NOK 782,000
Equity
NOK 2.0m
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.5%
Satisfactory
Equity as a share of total capital

Who owns TORKEL SCHIVE AS?

NI + TO AS
TORKEL SCHIVE AS
NOK 80.5m rev. · NOK 782,000 profit

TORKEL SCHIVE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORKEL SCHIVE AS own?

TORKEL SCHIVE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TORKEL SCHIVE AS

Who owns TORKEL SCHIVE AS?

NI + TO AS is the largest registered owner, with 100.0%.

What is the revenue of TORKEL SCHIVE AS?

TORKEL SCHIVE AS had revenue of NOK 80.5m in 2025.

Who is the general manager of TORKEL SCHIVE AS?

Torkel Schive is registered as general manager of TORKEL SCHIVE AS.

Where is TORKEL SCHIVE AS based?

TORKEL SCHIVE AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.