BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

KBL KONSULT AS

Org. no. 932079429 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 655,000
Equity NOK 424,000
Incorporated 2023
Employees 7
Share capital NOK 30,000

KBL KONSULT AS is registered as a limited company in Kristiansand, Agder with organisation number 932079429. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bemanningsbyrå, derav utleie av personell. Konsulenttjenester innen hotell, restaurant og catering. Catering. Produksjon av matvarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 655,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 655,000
Equity
NOK 424,000
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.2%
Good
Equity as a share of total capital

Who owns KBL KONSULT AS?

SVEIN LARSEN
KBL KONSULT AS
NOK 4.4m rev. · NOK 655,000 profit

KBL KONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KBL KONSULT AS own?

KBL KONSULT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KBL KONSULT AS

Who owns KBL KONSULT AS?

SVEIN LARSEN is the largest registered owner, with 100.0%.

What is the revenue of KBL KONSULT AS?

KBL KONSULT AS had revenue of NOK 4.4m in 2025.

Where is KBL KONSULT AS based?

KBL KONSULT AS has its business address in Kristiansand S.

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.