biztrac. BETA
COMPANY REGISTER PROFILE
935716713 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Operation of sports facilities

GUTTAKRUTT HOLDING AS

Org. no. 935716713 Limited company (AS) Bergen Incorporated 2025 Active
Operating profit NOK −380
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

GUTTAKRUTT HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 935716713. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investere i og forvalte aksjer og andeler i andre selskaper.”.

Former names: JNHS 106 AS

Key figures · 2025

Operating profit
NOK −380
Equity
NOK 23,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns GUTTAKRUTT HOLDING AS?

GUTTAKRUTT HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GUTTAKRUTT HOLDING AS own?

GUTTAKRUTT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GUTTAKRUTT HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about GUTTAKRUTT HOLDING AS

Who owns GUTTAKRUTT HOLDING AS?

Kristoffer Drange is the largest registered owner, with 50.0%.

Who is the general manager of GUTTAKRUTT HOLDING AS?

Kristoffer Drange is registered as general manager of GUTTAKRUTT HOLDING AS.

Where is GUTTAKRUTT HOLDING AS based?

GUTTAKRUTT HOLDING AS has its business address in Bergen.

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.