BIZTRAC BETA
Construction of residential and non-residential buildings

KJØLSTAD SAUR BYGG AS

Org. no. 913122526 Limited company (AS) Høylandet Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 205,000
Equity NOK 2.9m
Incorporated 2014
Share capital NOK 30,000

KJØLSTAD SAUR BYGG AS is registered as a limited company in Høylandet, Trøndelag with organisation number 913122526. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring, rehabilitering og vedlikehold av bygninger, samt annen virksomhet som står i forbindelse med dette. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 205,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 205,000
Equity
NOK 2.9m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns KJØLSTAD SAUR BYGG AS?

LASSE SAUR
KJØLSTAD SAUR BYGG AS
NOK 7.0m rev. · NOK 205,000 profit

KJØLSTAD SAUR BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KJØLSTAD SAUR BYGG AS

Who owns KJØLSTAD SAUR BYGG AS?

LASSE SAUR is the largest registered owner, with 50.0%.

What is the revenue of KJØLSTAD SAUR BYGG AS?

KJØLSTAD SAUR BYGG AS had revenue of NOK 7.0m in 2025.

Who is the general manager of KJØLSTAD SAUR BYGG AS?

Svein Erik Kjølstad is registered as general manager of KJØLSTAD SAUR BYGG AS.

Where is KJØLSTAD SAUR BYGG AS based?

KJØLSTAD SAUR BYGG AS has its business address in Høylandet.

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.