biztrac. BETA
COMPANY REGISTER PROFILE
913912551 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

KLINKEN AS

Org. no. 913912551 Limited company (AS) Stavanger Incorporated 2014 Active
Revenue 2025 NOK 300,000
Operating profit NOK −401,000
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 2.0m

Signals

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

KLINKEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 913912551. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 2.0m, divided into 2000000 shares. The company's stated purpose is: “Drive utvikling og utleie av fast eiendom, samt å investere i aksjer og alt som står i naturlig forbindelse med forannevnte.”. The most recent filed accounts, for the 2025 financial year, show NOK 300,000 in revenue and NOK −401,000 in operating profit.

Key figures · 2025

Revenue
NOK 300,000
▲ +3900 %
Operating profit
NOK −401,000
▲ +70 %
Equity
NOK 1.5m
▼ −31 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
-0.7%
Not satisfactory
Return on total assets
Solidity
1.9%
Not satisfactory
Equity as a share of total capital

Who owns KLINKEN AS?

KLINKEN AS
NOK 300,000 rev. · NOK −401,000 profit

KLINKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLINKEN AS

Who owns KLINKEN AS?

K2 BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of KLINKEN AS?

KLINKEN AS had revenue of NOK 300,000 in 2025.

Who is the general manager of KLINKEN AS?

Sigve Hebnes is registered as general manager of KLINKEN AS.

Where is KLINKEN AS based?

KLINKEN AS has its business address in Stavanger.

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.