BIZTRAC BETA
Other support activities to arts and performing arts

GAULDALSROCK AS

Org. no. 914320038 Limited company (AS) Melhus Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −378,000
Equity NOK −600,000
Incorporated 2014
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−600k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−378k kr).
  • Nylig endring 2026-03-03 Adresseendring registrert 2026-03-03.

GAULDALSROCK AS is registered as a limited company in Melhus, Trøndelag with organisation number 914320038. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Arrangere store og små kulturarrangementer i gauldalsregionen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −378,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −378,000
Equity
NOK −600,000

Financial health · 2025

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-189.6%
Weak
Equity as a share of total capital

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

Who owns GAULDALSROCK AS?

KRISTIAN LORVIK
GAULDALSROCK AS
NOK 1.0m rev. · NOK −378,000 profit

GAULDALSROCK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAULDALSROCK AS

Who owns GAULDALSROCK AS?

KRISTIAN LORVIK is the largest registered owner, with 50.0%.

What is the revenue of GAULDALSROCK AS?

GAULDALSROCK AS had revenue of NOK 1.0m in 2025.

Where is GAULDALSROCK AS based?

GAULDALSROCK AS has its business address in Melhus.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.