BIZTRAC BETA
Uoppgitt

TYTTA KAPITAL AS

Org. no. 923628231 Limited company (AS) Voss Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK −794,000
Equity NOK −734,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−734k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−794k kr).

TYTTA KAPITAL AS is registered as a limited company in Voss, Vestland with organisation number 923628231. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av å investere i aksjer og selskap som driver med lojalitetsbyggende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK −794,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK −794,000
Equity
NOK −734,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12236466.7%
Weak
Equity as a share of total capital

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

Who owns TYTTA KAPITAL AS?

TYTTA BOLSTAD
TYTTA KAPITAL AS
NOK 20,000 rev. · NOK −794,000 profit

TYTTA KAPITAL AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TYTTA KAPITAL AS

Who owns TYTTA KAPITAL AS?

TYTTA BOLSTAD is the largest registered owner, with 30.0%.

What is the revenue of TYTTA KAPITAL AS?

TYTTA KAPITAL AS had revenue of NOK 20,000 in 2025.

Who is the general manager of TYTTA KAPITAL AS?

Tytta Bolstad is registered as general manager of TYTTA KAPITAL AS.

Where is TYTTA KAPITAL AS based?

TYTTA KAPITAL 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.