biztrac. BETA
COMPANY REGISTER PROFILE
934874021 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KULP HOLDING AS

Org. no. 934874021 Limited company (AS) Time Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −810
Equity NOK 29,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−810 kr).

KULP HOLDING AS is registered as a limited company in Time, Rogaland with organisation number 934874021. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper og forvalte disse, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −810 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −810
Equity
NOK 29,000
Est. value
NOK 34,000

Financial health · 2025

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

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

Who owns KULP HOLDING AS?

KULP HOLDING AS
NOK 0 rev. · NOK −810 profit

KULP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KULP HOLDING AS own?

KULP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KULP HOLDING AS

Who owns KULP HOLDING AS?

Bjørn Tore Søyland is the largest registered owner, with 100.0%.

What is the revenue of KULP HOLDING AS?

KULP HOLDING AS had revenue of NOK 0 in 2025.

Where is KULP HOLDING AS based?

KULP HOLDING AS has its business address in Bryne.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.