BIZTRAC BETA
Development of building projects

TRYSIL KNUT HORISONT UTVIKLING AS

Org. no. 927603349 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −31,000
Equity NOK −475,000
Incorporated 2021
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−475k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−31k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRYSIL KNUT HORISONT UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 927603349. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie og utvikle tomter og fast eiendom for salg og utleie, samt hva herved står i forbindelse, herunder delta i andre selskaper med liknende virksomhet.”.

Key figures · 2024

Operating profit
NOK −31,000
Equity
NOK −475,000

Financial health · 2024

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

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

Who owns TRYSIL KNUT HORISONT UTVIKLING AS?

ORAKEL HOLDING AS
TRYSIL KNUT HORISONT UTVIKLING AS
· NOK −31,000 profit

TRYSIL KNUT HORISONT UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYSIL KNUT HORISONT UTVIKLING AS

Who owns TRYSIL KNUT HORISONT UTVIKLING AS?

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

Where is TRYSIL KNUT HORISONT UTVIKLING AS based?

TRYSIL KNUT HORISONT UTVIKLING AS has its business address in Oslo.

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.