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

BETONGKUTTEREN AS

Org. no. 991248854 Limited company (AS) Kristiansand Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 8.0m
Operating profit NOK 990,000
Equity NOK 1.3m
Incorporated 2007
Share capital NOK 100,000

Signals

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

BETONGKUTTEREN AS is registered as a limited company in Kristiansand, Agder with organisation number 991248854. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Betongkutting samt hva som står i naturlig forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.0m in revenue and NOK 990,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.0m
Operating profit
NOK 990,000
Equity
NOK 1.3m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns BETONGKUTTEREN AS?

VERDAL OG TRYSNES AS
BETONGKUTTEREN AS
NOK 8.0m rev. · NOK 990,000 profit

BETONGKUTTEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BETONGKUTTEREN AS

Who owns BETONGKUTTEREN AS?

VERDAL OG TRYSNES AS is the largest registered owner, with 100.0%.

What is the revenue of BETONGKUTTEREN AS?

BETONGKUTTEREN AS had revenue of NOK 8.0m in 2024.

Who is the general manager of BETONGKUTTEREN AS?

Kenneth Vildalen Trysnes is registered as general manager of BETONGKUTTEREN AS.

Where is BETONGKUTTEREN AS based?

BETONGKUTTEREN AS has its business address in Søgne.

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.