BIZTRAC BETA
Other specialised construction activities n.e.c.

POL BETONG AS

Org. no. 996467775 Limited company (AS) Sarpsborg Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 44.8m
Operating profit NOK −289,000
Equity NOK 13.6m
Incorporated 2011
Employees 81
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−289k kr).

POL BETONG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 996467775. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2011 and has 81 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Prosjektarbeid innenfor mur og betong, samt annet som naturlig hører under virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 44.8m in revenue and NOK −289,000 in operating profit.

Key figures · 2024

Revenue
NOK 44.8m
Operating profit
NOK −289,000
Equity
NOK 13.6m
Est. value
NOK 20.8m

Financial health · 2024

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

Who owns POL BETONG AS?

ROBERT KAZIMIERZ LILLA
POL BETONG AS
NOK 44.8m rev. · NOK −289,000 profit

POL BETONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about POL BETONG AS

Who owns POL BETONG AS?

ROBERT KAZIMIERZ LILLA is the largest registered owner, with 51.0%.

What is the revenue of POL BETONG AS?

POL BETONG AS had revenue of NOK 44.8m in 2024.

Who is the general manager of POL BETONG AS?

Robert Kazimierz Lilla is registered as general manager of POL BETONG AS.

Where is POL BETONG AS based?

POL BETONG AS has its business address in Grålum.

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.