biztrac. BETA
COMPANY REGISTER PROFILE
934935837 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

KULTURKAFEEN VALHALL AS

Org. no. 934935837 Limited company (AS) Nesbyen Incorporated 1983 Active
Revenue 2025 NOK 2.5m
Operating profit NOK 1.8m
Equity NOK 1.9m
Incorporated 1983
Share capital NOK 154,000

KULTURKAFEEN VALHALL AS is registered as a limited company in Nesbyen, Buskerud with organisation number 934935837. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1983. Registered share capital is NOK 154,000, divided into 77 shares. The company's stated purpose is: “Cafévirksomhet, samt investering i fast eiendom og aksjer og det som naturlig hører under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.8m in operating profit.

Former names: AS Støpas

Key figures · 2025

Revenue
NOK 2.5m
▲ +547 %
Operating profit
NOK 1.8m
▲ +7766 %
Equity
NOK 1.9m
▼ −37 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
42.7%
Very good
Return on total assets
Solidity
38.5%
Good
Equity as a share of total capital

Who owns KULTURKAFEEN VALHALL AS?

KULTURKAFEEN VALHALL AS
NOK 2.5m rev. · NOK 1.8m profit

KULTURKAFEEN VALHALL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KULTURKAFEEN VALHALL AS

Who owns KULTURKAFEEN VALHALL AS?

Terje Gewelt is the largest registered owner, with 100.0%.

What is the revenue of KULTURKAFEEN VALHALL AS?

KULTURKAFEEN VALHALL AS had revenue of NOK 2.5m in 2025.

Who is the general manager of KULTURKAFEEN VALHALL AS?

Terje Gewelt is registered as general manager of KULTURKAFEEN VALHALL AS.

Where is KULTURKAFEEN VALHALL AS based?

KULTURKAFEEN VALHALL AS has its business address in Nesbyen.

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.