BIZTRAC BETA
Site preparation

SGO ENTREPRENØR AS

Org. no. 915714560 Limited company (AS) Selbu Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −130,000
Equity NOK −2.1m
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−130k kr).

SGO ENTREPRENØR AS is registered as a limited company in Selbu, Trøndelag with organisation number 915714560. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Graving og massetransport, samt oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −130,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −130,000
Equity
NOK −2.1m

Financial health · 2024

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

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

Who owns SGO ENTREPRENØR AS?

GRIM OLE BOLMØYEN
SGO ENTREPRENØR AS
NOK 1.9m rev. · NOK −130,000 profit

SGO ENTREPRENØR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SGO ENTREPRENØR AS

Who owns SGO ENTREPRENØR AS?

GRIM OLE BOLMØYEN is the largest registered owner, with 53.3%.

What is the revenue of SGO ENTREPRENØR AS?

SGO ENTREPRENØR AS had revenue of NOK 1.9m in 2025.

Who is the general manager of SGO ENTREPRENØR AS?

Grim Ole Bolmøyen is registered as general manager of SGO ENTREPRENØR AS.

Where is SGO ENTREPRENØR AS based?

SGO ENTREPRENØR AS has its business address in Selbu.

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.