BIZTRAC BETA
Construction of residential and non-residential buildings

BORGAR KOLBJØRNSRUD AS

Org. no. 919204621 Limited company (AS) Sigdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 584,000
Equity NOK 1.8m
Incorporated 2017
Share capital NOK 100,000

BORGAR KOLBJØRNSRUD AS is registered as a limited company in Sigdal, Buskerud with organisation number 919204621. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tømrervirksomhet, oppføring og restaurering av eiendommer, samt maskinentreprenørvirksomhet og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 584,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 584,000
Equity
NOK 1.8m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns BORGAR KOLBJØRNSRUD AS?

BORGAR KOLBJØRNSRUD
BORGAR KOLBJØRNSRUD AS
NOK 3.6m rev. · NOK 584,000 profit

BORGAR KOLBJØRNSRUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGAR KOLBJØRNSRUD AS

Who owns BORGAR KOLBJØRNSRUD AS?

BORGAR KOLBJØRNSRUD is the largest registered owner, with 100.0%.

What is the revenue of BORGAR KOLBJØRNSRUD AS?

BORGAR KOLBJØRNSRUD AS had revenue of NOK 3.6m in 2025.

Who is the general manager of BORGAR KOLBJØRNSRUD AS?

Borgar Kolbjørnsrud is registered as general manager of BORGAR KOLBJØRNSRUD AS.

Where is BORGAR KOLBJØRNSRUD AS based?

BORGAR KOLBJØRNSRUD AS has its business address in Eggedal.

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.