BIZTRAC BETA
Civil engineering activities

SYLTE TECH AS

Org. no. 914179483 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 664,000
Operating profit NOK 562,000
Equity NOK 1.8m
Incorporated 2014
Share capital NOK 30,000

SYLTE TECH AS is registered as a limited company in Drammen, Buskerud with organisation number 914179483. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor sikkerhet å bistå kunder slik at de får rette løsninger. Rådgi i forbindelse med innkjøp av varer og tjenester. Prosjektering og kontroll av prosjektering innenfor sikkerhet. Kontroll av utførelse innenfor sikkerhet. Prosjektledelse. Kursing.”. The most recent filed accounts, for the 2024 financial year, show NOK 664,000 in revenue and NOK 562,000 in operating profit.

Key figures · 2024

Revenue
NOK 664,000
Operating profit
NOK 562,000
Equity
NOK 1.8m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.9%
Very good
Equity as a share of total capital

Who owns SYLTE TECH AS?

ØYVIN MICHAL SYLTE
SYLTE TECH AS
NOK 664,000 rev. · NOK 562,000 profit

SYLTE TECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYLTE TECH AS

Who owns SYLTE TECH AS?

ØYVIN MICHAL SYLTE is the largest registered owner, with 100.0%.

What is the revenue of SYLTE TECH AS?

SYLTE TECH AS had revenue of NOK 664,000 in 2024.

Who is the general manager of SYLTE TECH AS?

Øyvin Michal Sylte is registered as general manager of SYLTE TECH AS.

Where is SYLTE TECH AS based?

SYLTE TECH AS has its business address in Mjøndalen.

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.