BIZTRAC BETA
Business and other management consultancy activities

KREGEN HOLDING AS

Org. no. 919966548 Limited company (AS) Sandnes Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 492,000
Equity NOK 2.5m
Incorporated 2017
Share capital NOK 30,000

KREGEN HOLDING AS is registered as a limited company in Sandnes, Rogaland with organisation number 919966548. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i andre selskaper samt drive med rådgivning og ledelse av andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 492,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 492,000
Equity
NOK 2.5m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns KREGEN HOLDING AS?

TERJE BORSHEIM
KREGEN HOLDING AS
NOK 1.7m rev. · NOK 492,000 profit

KREGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KREGEN HOLDING AS own?

KREGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KREGEN HOLDING AS

Who owns KREGEN HOLDING AS?

TERJE BORSHEIM is the largest registered owner, with 100.0%.

What is the revenue of KREGEN HOLDING AS?

KREGEN HOLDING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of KREGEN HOLDING AS?

Terje Borsheim is registered as general manager of KREGEN HOLDING AS.

Where is KREGEN HOLDING AS based?

KREGEN HOLDING AS has its business address in Sandnes.

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.