BIZTRAC BETA
Construction of residential and non-residential buildings

KBG AS

Org. no. 932498340 Limited company (AS) Kinn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 41,000
Equity NOK 32,000
Incorporated 2023
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KBG AS is registered as a limited company in Kinn, Vestland with organisation number 932498340. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 41,000
Equity
NOK 32,000
Est. value
NOK 133,000

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KBG AS?

GOTTEBERGE HOLDING AS
KBG AS
NOK 4.4m rev. · NOK 41,000 profit

KBG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KBG AS er morselskap for 1 datterselskap:

Frequently asked questions about KBG AS

Who owns KBG AS?

GOTTEBERGE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KBG AS?

KBG AS had revenue of NOK 4.4m in 2025.

Who is the general manager of KBG AS?

Kephas Kaspar Kalisch is registered as general manager of KBG AS.

Where is KBG AS based?

KBG AS has its business address in Raudeberg.

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.