biztrac. BETA
COMPANY REGISTER PROFILE
933798550 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KRØST AS

Org. no. 933798550 Limited company (AS) Kristiansand Incorporated 2024 Active
Revenue 2025 NOK 61,000
Operating profit NOK −15,000
Equity NOK 2,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KRØST AS is registered as a limited company in Kristiansand, Agder with organisation number 933798550. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift og utleie av fast eiendom og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 61,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 61,000
Operating profit
NOK −15,000
▼ −128 %
Equity
NOK 2,000
▼ −86 %
Est. value
NOK 2,000

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
-2.2%
Not satisfactory
Return on total assets
Solidity
0.2%
Weak
Equity as a share of total capital

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

Who owns KRØST AS?

KRØST AS
NOK 61,000 rev. · NOK −15,000 profit

KRØST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRØST AS

Who owns KRØST AS?

TRYLAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KRØST AS?

KRØST AS had revenue of NOK 61,000 in 2025.

Who is the general manager of KRØST AS?

Stian Tryland is registered as general manager of KRØST AS.

Where is KRØST AS based?

KRØST AS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.