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

KLENGSTOVA AS

Org. no. 993220361 Limited company (AS) Voss Incorporated 2008 Active
Revenue 2025 NOK 365,000
Operating profit NOK −110,000
Equity NOK 196,000
Incorporated 2008
Share capital NOK 100,000

Signals

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

KLENGSTOVA AS is registered as a limited company in Voss, Vestland with organisation number 993220361. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive fast eiendom samt hva med dette hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 365,000 in revenue and NOK −110,000 in operating profit.

Key figures · 2025

Revenue
NOK 365,000
▼ −24 %
Operating profit
NOK −110,000
▼ −128 %
Equity
NOK 196,000
▼ −31 %
Est. value
NOK 371,000

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

Who owns KLENGSTOVA AS?

KLENGSTOVA AS
NOK 365,000 rev. · NOK −110,000 profit

KLENGSTOVA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLENGSTOVA AS

Who owns KLENGSTOVA AS?

BJØRN BRUNBORG AS is the largest registered owner, with 100.0%.

What is the revenue of KLENGSTOVA AS?

KLENGSTOVA AS had revenue of NOK 365,000 in 2025.

Who is the general manager of KLENGSTOVA AS?

Bjørn Helge Brunborg is registered as general manager of KLENGSTOVA AS.

Where is KLENGSTOVA AS based?

KLENGSTOVA AS has its business address in Voss.

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.