BIZTRAC BETA
Construction of residential and non-residential buildings

GR BYGGENTREPRENØR AS

Org. no. 927932555 Limited company (AS) Sør-Odal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 691,000
Equity NOK 1.3m
Incorporated 2021
Employees 7
Share capital NOK 300,000

GR BYGGENTREPRENØR AS is registered as a limited company in Sør-Odal, Innlandet with organisation number 927932555. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 7 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Tømrer og snekkervirksomhet innen nybygg og rehabilitering, samt virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 691,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 691,000
Equity
NOK 1.3m
Est. value
NOK 3.0m

Financial health · 2024

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.9%
Very good
Equity as a share of total capital

Who owns GR BYGGENTREPRENØR AS?

GR-GRUPPEN AS
GR BYGGENTREPRENØR AS
NOK 10.1m rev. · NOK 691,000 profit

GR BYGGENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GR BYGGENTREPRENØR AS

Who owns GR BYGGENTREPRENØR AS?

GR-GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of GR BYGGENTREPRENØR AS?

GR BYGGENTREPRENØR AS had revenue of NOK 10.1m in 2024.

Who is the general manager of GR BYGGENTREPRENØR AS?

Rune Gaustad is registered as general manager of GR BYGGENTREPRENØR AS.

Where is GR BYGGENTREPRENØR AS based?

GR BYGGENTREPRENØR AS has its business address in Skarnes.

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.