BIZTRAC BETA
Development of building projects

TRYKON BOLIGUTVIKLING AS

Org. no. 918784535 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 29.9m
Operating profit NOK 1.7m
Equity NOK 1.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRYKON BOLIGUTVIKLING AS is registered as a limited company in Drammen, Buskerud with organisation number 918784535. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling, salg, drift og forvaltning av eiendom, samt finansiering og dertil beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 29.9m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 29.9m
Operating profit
NOK 1.7m
Equity
NOK 1.7m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns TRYKON BOLIGUTVIKLING AS?

TRYSILHUS TRYKON AS
TRYKON BOLIGUTVIKLING AS
NOK 29.9m rev. · NOK 1.7m profit

TRYKON BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYKON BOLIGUTVIKLING AS

Who owns TRYKON BOLIGUTVIKLING AS?

TRYSILHUS TRYKON AS is the largest registered owner, with 100.0%.

What is the revenue of TRYKON BOLIGUTVIKLING AS?

TRYKON BOLIGUTVIKLING AS had revenue of NOK 29.9m in 2024.

Where is TRYKON BOLIGUTVIKLING AS based?

TRYKON BOLIGUTVIKLING AS has its business address in Drammen.

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.