BIZTRAC BETA
Site preparation

GR ANLEGG AS

Org. no. 932755963 Limited company (AS) Vinje Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 46,000
Equity NOK 85,000
Incorporated 2023
Share capital NOK 50,000

GR ANLEGG AS is registered as a limited company in Vinje, Telemark with organisation number 932755963. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Maskinarbeid, tunnelarbeid, transport, utleie av utstyr og arbeidskraft, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer. Samt annen virksomhet som står naturlig tilknytning til dette. Herunder deltaking i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 46,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 46,000
Equity
NOK 85,000
Est. value
NOK 205,000

Financial health · 2024

Liquidity
2.70
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
72.7%
Weak
Equity as a share of total capital

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

Who owns GR ANLEGG AS?

KNUT AASMUND GROVEN RINGHUS
GR ANLEGG AS
NOK 1.6m rev. · NOK 46,000 profit

GR ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GR ANLEGG AS

Who owns GR ANLEGG AS?

KNUT AASMUND GROVEN RINGHUS is the largest registered owner, with 100.0%.

What is the revenue of GR ANLEGG AS?

GR ANLEGG AS had revenue of NOK 1.6m in 2024.

Who is the general manager of GR ANLEGG AS?

Knut Aasmund Groven Ringhus is registered as general manager of GR ANLEGG AS.

Where is GR ANLEGG AS based?

GR ANLEGG AS has its business address in Vinje.

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.