BIZTRAC BETA
Extraction of peat

FROSTA TORV AS

Org. no. 880806882 Limited company (AS) Frosta Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 458,000
Operating profit NOK −256,000
Equity NOK 50,000
Incorporated 1999
Share capital NOK 100,000

Signals

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

FROSTA TORV AS is registered as a limited company in Frosta, Trøndelag with organisation number 880806882. The business is classified under extraction of peat (NACE 08.920). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av torv og jordforbedringsmidler og det som naturlig følger med slik virksomhet, samt å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 458,000 in revenue and NOK −256,000 in operating profit.

Key figures · 2025

Revenue
NOK 458,000
Operating profit
NOK −256,000
Equity
NOK 50,000
Est. value
NOK 368,000

Financial health · 2024

Liquidity
2.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
59.5%
Weak
Equity as a share of total capital

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

Who owns FROSTA TORV AS?

KARIN VIKASKAG NORDAHL
FROSTA TORV AS
NOK 458,000 rev. · NOK −256,000 profit

FROSTA TORV AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FROSTA TORV AS

Who owns FROSTA TORV AS?

KARIN VIKASKAG NORDAHL is the largest registered owner, with 50.0%.

What is the revenue of FROSTA TORV AS?

FROSTA TORV AS had revenue of NOK 458,000 in 2025.

Who is the general manager of FROSTA TORV AS?

Svein Henry Nordahl is registered as general manager of FROSTA TORV AS.

Where is FROSTA TORV AS based?

FROSTA TORV AS has its business address in Frosta.

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.