BIZTRAC BETA
Manufacture of ready-mixed concrete

SYLTEOSEN BETONG AS

Org. no. 993460788 Limited company (AS) Hustadvika Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 65.9m
Operating profit NOK 3.9m
Equity NOK 36.3m
Incorporated 2008
Employees 31
Share capital NOK 150,000

SYLTEOSEN BETONG AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 993460788. The business is classified under manufacture of ready-mixed concrete (NACE 23.630). The company was incorporated in 2008 and has 31 registered employees. Registered share capital is NOK 150,000, divided into 333 shares. The company's stated purpose is: “Produksjon og levering av betong samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 65.9m in revenue and NOK 3.9m in operating profit.

Key figures · 2024

Revenue
NOK 65.9m
Operating profit
NOK 3.9m
Equity
NOK 36.3m
Est. value
NOK 38.1m

Financial health · 2024

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
74.2%
Very good
Equity as a share of total capital

Who owns SYLTEOSEN BETONG AS?

SYLTEOSEN INVEST AS
SYLTEOSEN BETONG AS
NOK 65.9m rev. · NOK 3.9m profit

SYLTEOSEN BETONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYLTEOSEN BETONG AS

Who owns SYLTEOSEN BETONG AS?

SYLTEOSEN INVEST AS is the largest registered owner, with 60.1%.

What is the revenue of SYLTEOSEN BETONG AS?

SYLTEOSEN BETONG AS had revenue of NOK 65.9m in 2024.

Who is the general manager of SYLTEOSEN BETONG AS?

Thomas Øyen Fleten is registered as general manager of SYLTEOSEN BETONG AS.

Where is SYLTEOSEN BETONG AS based?

SYLTEOSEN BETONG AS has its business address in Elnesvågen.

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.