BIZTRAC BETA
Growing of pome fruits and stone fruits

TORHEIM/SKJERDAL AS

Org. no. 922983968 Limited company (AS) Aurland Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 249,000
Operating profit NOK 31,000
Equity NOK 73,000
Incorporated 2019
Share capital NOK 30,000

TORHEIM/SKJERDAL AS is registered as a limited company in Aurland, Vestland with organisation number 922983968. The business is classified under growing of pome fruits and stone fruits (NACE 01.240). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fruktproduksjon, språktenester; konsulenttenester; korrekturlesing og språkvask, yoga; kurs, workshops og retreats.”. The most recent filed accounts, for the 2024 financial year, show NOK 249,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2024

Revenue
NOK 249,000
Operating profit
NOK 31,000
Equity
NOK 73,000
Est. value
NOK 143,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TORHEIM/SKJERDAL AS?

ANNE MARIE TORHEIM
TORHEIM/SKJERDAL AS
NOK 249,000 rev. · NOK 31,000 profit

TORHEIM/SKJERDAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TORHEIM/SKJERDAL AS

Who owns TORHEIM/SKJERDAL AS?

ANNE MARIE TORHEIM is the largest registered owner, with 50.0%.

What is the revenue of TORHEIM/SKJERDAL AS?

TORHEIM/SKJERDAL AS had revenue of NOK 249,000 in 2024.

Who is the general manager of TORHEIM/SKJERDAL AS?

Haakon Skjerdal is registered as general manager of TORHEIM/SKJERDAL AS.

Where is TORHEIM/SKJERDAL AS based?

TORHEIM/SKJERDAL AS has its business address in Aurland.

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.