BIZTRAC BETA
Construction of residential and non-residential buildings

KC BYGG AS

Org. no. 988807494 Limited company (AS) Lillesand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 17.6m
Operating profit NOK 1.0m
Equity NOK 2.9m
Incorporated 2005
Employees 12
Share capital NOK 100,000

KC BYGG AS is registered as a limited company in Lillesand, Agder with organisation number 988807494. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utførelse av håndverkstjenester, rehabilitering og vedlikeholdstjenester innen bygg og anleggsbransjen, herunder investering, kjøp, salg og utleie av fast eiendom, samt deltakelse i andre selskap og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.6m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 17.6m
Operating profit
NOK 1.0m
Equity
NOK 2.9m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns KC BYGG AS?

GRAMOD AS
KC BYGG AS
NOK 17.6m rev. · NOK 1.0m profit

KC BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KC BYGG AS

Who owns KC BYGG AS?

GRAMOD AS is the largest registered owner, with 100.0%.

What is the revenue of KC BYGG AS?

KC BYGG AS had revenue of NOK 17.6m in 2024.

Who is the general manager of KC BYGG AS?

Håvard Thomassen is registered as general manager of KC BYGG AS.

Where is KC BYGG AS based?

KC BYGG AS has its business address in Lillesand.

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.