biztrac. BETA
COMPANY REGISTER PROFILE
928780414 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

KRUSE ANLEGG-VEST ANS

Org. no. 928780414 General partnership (ANS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK −6.6m
Operating profit NOK 1,000
Equity NOK 15.3m
Incorporated 2022

KRUSE ANLEGG-VEST ANS is registered as a general partnership in Kristiansand, Agder with organisation number 928780414. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. The company's stated purpose is: “Å utføre entreprenørarbeider som hovedentreprise i tilknytning til kontrakt med Boliden Odda AS for prosjekt Green Zink Odda, og alt som står i den forbindelse. Arbeidsfellesskapet er utelukkende for dette oppdraget og skal ikke innebære et fast samarbeidsforhold mellom partene.”. The most recent filed accounts, for the 2025 financial year, show NOK −6.6m in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK −6.6m
▼ −102 %
Operating profit
NOK 1,000
▼ −100 %
Equity
NOK 15.3m
▲ +4 %
Est. value
NOK 63.9m

Financial health · 2025

Liquidity
3.01
Very good
Current assets ÷ current liabilities
Profitability
1.3%
Weak
Return on total assets
Solidity
66.8%
Very good
Equity as a share of total capital

Who owns KRUSE ANLEGG-VEST ANS?

No shareholders are registered for KRUSE ANLEGG-VEST ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KRUSE ANLEGG-VEST ANS

What is the revenue of KRUSE ANLEGG-VEST ANS?

KRUSE ANLEGG-VEST ANS had revenue of NOK −6.6m in 2025.

Who is the general manager of KRUSE ANLEGG-VEST ANS?

Bjørn Velken is registered as general manager of KRUSE ANLEGG-VEST ANS.

Where is KRUSE ANLEGG-VEST ANS based?

KRUSE ANLEGG-VEST ANS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.