BIZTRAC BETA
Arts creation activities in literature

I. TORPE AS

Org. no. 935622557 Limited company (AS) Voss Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 41,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

I. TORPE AS is registered as a limited company in Voss, Vestland with organisation number 935622557. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Produksjon og formidling av journalistisk innhald og anna som fell naturleg inn under dette, samt deltaking i andre selskap, investeringar og nærliggande verksemd.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 41,000
Est. value
NOK 51,000

Financial health · 2025

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

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

Who owns I. TORPE AS?

INGVIL AAEN TORPE
I. TORPE AS
NOK 0 rev. · NOK −2,000 profit

I. TORPE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does I. TORPE AS own?

I. TORPE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about I. TORPE AS

Who owns I. TORPE AS?

INGVIL AAEN TORPE is the largest registered owner, with 100.0%.

What is the revenue of I. TORPE AS?

I. TORPE AS had revenue of NOK 0 in 2025.

Where is I. TORPE AS based?

I. TORPE AS has its business address in Voss.

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.