BIZTRAC BETA
Construction of residential and non-residential buildings

KE BYGG AS

Org. no. 912663019 Limited company (AS) Nannestad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 12.3m
Operating profit NOK 1.8m
Equity NOK 3.2m
Incorporated 2013
Employees 5
Share capital NOK 30,000

KE BYGG AS is registered as a limited company in Nannestad, Akershus with organisation number 912663019. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive bygge- og entreprenørvirksomhet, eiendomsutleie, utleie av maskiner, utstyr og kjøretøy, samt tilknyttet kommersiell virksomhet. Selskapet kan også investere i og delta i andre selskaper, herunder kjøp og salg av aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.3m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 12.3m
Operating profit
NOK 1.8m
Equity
NOK 3.2m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns KE BYGG AS?

KAROLIS BRIEDIS
KE BYGG AS
NOK 12.3m rev. · NOK 1.8m profit

KE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KE BYGG AS

Who owns KE BYGG AS?

KAROLIS BRIEDIS is the largest registered owner, with 100.0%.

What is the revenue of KE BYGG AS?

KE BYGG AS had revenue of NOK 12.3m in 2024.

Who is the general manager of KE BYGG AS?

Karolis Briedis is registered as general manager of KE BYGG AS.

Where is KE BYGG AS based?

KE BYGG AS has its business address in Holter.

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.