BIZTRAC BETA
Contract catering service activities and other food service activities

KRIPTA AS

Org. no. 922687803 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 68,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

KRIPTA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922687803. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Delta i andre selskaper, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 68,000
Est. value
NOK 6.1m

Financial health · 2024

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

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

Who owns KRIPTA AS?

UGLAKIOSKEN AS
KRIPTA AS
NOK 0 rev. · NOK −10,000 profit

KRIPTA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KRIPTA AS own?

KRIPTA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KRIPTA AS

Who owns KRIPTA AS?

UGLAKIOSKEN AS is the largest registered owner, with 50.0%.

What is the revenue of KRIPTA AS?

KRIPTA AS had revenue of NOK 0 in 2024.

Where is KRIPTA AS based?

KRIPTA AS has its business address in Heimdal.

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.