biztrac. BETA
COMPANY REGISTER PROFILE
921332459 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

TORHEIM ANLEGG AS

Org. no. 921332459 Limited company (AS) Tønsberg Incorporated 2018 Active
Revenue 2025 NOK 46,000
Operating profit NOK −28,000
Equity NOK 126,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

TORHEIM ANLEGG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 921332459. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Div transport, anlegg/graving, landbrukstjenester, fjell og bergverk, skogbruk, verksted.”. The most recent filed accounts, for the 2025 financial year, show NOK 46,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 46,000
▲ +127 %
Operating profit
NOK −28,000
▲ +32 %
Equity
NOK 126,000
▼ −18 %
Est. value
NOK 70,000

Financial health · 2025

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

Who owns TORHEIM ANLEGG AS?

TORHEIM ANLEGG AS
NOK 46,000 rev. · NOK −28,000 profit

TORHEIM ANLEGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TORHEIM ANLEGG AS

Who owns TORHEIM ANLEGG AS?

Per Tommy Torheim is the largest registered owner, with 70.0%.

What is the revenue of TORHEIM ANLEGG AS?

TORHEIM ANLEGG AS had revenue of NOK 46,000 in 2025.

Who is the general manager of TORHEIM ANLEGG AS?

Per Tommy Torheim is registered as general manager of TORHEIM ANLEGG AS.

Where is TORHEIM ANLEGG AS based?

TORHEIM ANLEGG AS has its business address in Ramnes.

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.