biztrac. BETA
COMPANY REGISTER PROFILE
928754677 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of roads and motorways

KSR ANS

Org. no. 928754677 General partnership (ANS) Hå Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 244.3m
Operating profit NOK −20.0m
Equity NOK 25.6m
Incorporated 2022

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20,0 mill kr).

KSR ANS is registered as a general partnership in Hå, Rogaland with organisation number 928754677. The business is classified under construction of roads and motorways (NACE 42.110). The company was incorporated in 2022. The company's stated purpose is: “Å utføre entreprenørarbeider som hovedentreprise i tilknytning til Statens vegvesens utlyste kontrakt for Prosjekt Fv. 44 Bussveien Stasjonsveien - Gauselvågen, 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 244.3m in revenue and NOK −20.0m in operating profit.

Key figures · 2025

Revenue
NOK 244.3m
▼ −53 %
Operating profit
NOK −20.0m
▼ −219 %
Equity
NOK 25.6m
▼ −43 %
Est. value
NOK 14.8m

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
-15.4%
Not satisfactory
Return on total assets
Solidity
31.7%
Good
Equity as a share of total capital

Who owns KSR ANS?

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

Frequently asked questions about KSR ANS

What is the revenue of KSR ANS?

KSR ANS had revenue of NOK 244.3m in 2025.

Who is the general manager of KSR ANS?

Tommy Emil Karlsson is registered as general manager of KSR ANS.

Where is KSR ANS based?

KSR ANS has its business address in Nærbø.

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.