BIZTRAC BETA
Site preparation

OK ANLEGGSSERVICE AS

Org. no. 984797540 Limited company (AS) Drammen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 290,000
Operating profit NOK −108,000
Equity NOK 94,000
Incorporated 2002
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−108k kr).

OK ANLEGGSSERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 984797540. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Anleggsvirksomhet, graving, planering og drenering.”. The most recent filed accounts, for the 2025 financial year, show NOK 290,000 in revenue and NOK −108,000 in operating profit.

Key figures · 2025

Revenue
NOK 290,000
Operating profit
NOK −108,000
Equity
NOK 94,000
Est. value
NOK 142,000

Financial health · 2025

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

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

Who owns OK ANLEGGSSERVICE AS?

KATIRCI HOLDING AS
OK ANLEGGSSERVICE AS
NOK 290,000 rev. · NOK −108,000 profit

OK ANLEGGSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OK ANLEGGSSERVICE AS

Who owns OK ANLEGGSSERVICE AS?

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

What is the revenue of OK ANLEGGSSERVICE AS?

OK ANLEGGSSERVICE AS had revenue of NOK 290,000 in 2025.

Who is the general manager of OK ANLEGGSSERVICE AS?

Adem Katirci is registered as general manager of OK ANLEGGSSERVICE AS.

Where is OK ANLEGGSSERVICE AS based?

OK ANLEGGSSERVICE 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.