BIZTRAC BETA
Other technical consultancy

GRUVO AS

Org. no. 919680423 Limited company (AS) Sokndal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 49,000
Equity NOK 161,000
Incorporated 2017
Share capital NOK 30,000

GRUVO AS is registered as a limited company in Sokndal, Rogaland with organisation number 919680423. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Produksjon, kjøp og salg av kunst og andre varer og tjenester som har naturlig tilknytning til dette. Bedrive kulturell virksomhet, herunder konsulenttjenester, instruksjon, kurs og workshop innen visuell kunst. Utforming av illustrasjon, grafisk design, webdesign, logodesign samt tilhørende tjenester. Konsulentbistand kontortjenester, KHMS system og annet som naturlig faller sammen med dette. Selskapet kan også eie eller delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 49,000
Equity
NOK 161,000
Est. value
NOK 321,000

Financial health · 2025

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.2%
Good
Equity as a share of total capital

Who owns GRUVO AS?

LENE DANIELSEN
GRUVO AS
NOK 1.8m rev. · NOK 49,000 profit

GRUVO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRUVO AS

Who owns GRUVO AS?

LENE DANIELSEN is the largest registered owner, with 90.0%.

What is the revenue of GRUVO AS?

GRUVO AS had revenue of NOK 1.8m in 2025.

Where is GRUVO AS based?

GRUVO AS has its business address in Hauge I Dalane.

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.