biztrac. BETA
COMPANY REGISTER PROFILE
989131958 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KRISTENBRUKET AS

Org. no. 989131958 Limited company (AS) Birkenes Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 967,000
Incorporated 2005
Share capital NOK 112,000

Signals

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

KRISTENBRUKET AS is registered as a limited company in Birkenes, Agder with organisation number 989131958. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 112,000, divided into 112 shares. The company's stated purpose is: “Investering i aksjer, andre selskapsandeler og fast eiendom, handels- og agenturvirksomhet innenfor sports- og fritidsbransjen, samt annet som står i forbindelse med dette, herunder eie andeler i selskaper med tilsvarende formål. Undervisningstjenester og annet som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −39,000
▼ −261 %
Equity
NOK 967,000
▲ +15 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
100.44
Very good
Current assets ÷ current liabilities
Profitability
7.9%
Satisfactory
Return on total assets
Solidity
99.2%
Very good
Equity as a share of total capital

Who owns KRISTENBRUKET AS?

KRISTENBRUKET AS
· NOK −39,000 profit

KRISTENBRUKET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRISTENBRUKET AS own?

KRISTENBRUKET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRISTENBRUKET AS

Who owns KRISTENBRUKET AS?

Hilde Røyseland Høygilt is the largest registered owner, with 100.0%.

Where is KRISTENBRUKET AS based?

KRISTENBRUKET AS has its business address in Birkeland.

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.