biztrac. BETA
COMPANY REGISTER PROFILE
919276614 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

GSG MASKIN AS

Org. no. 919276614 Limited company (AS) Overhalla Incorporated 2017 Active
Revenue 2025 NOK 6,000
Operating profit NOK −1,000
Equity NOK 6,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

GSG MASKIN AS is registered as a limited company in Overhalla, Trøndelag with organisation number 919276614. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av arbeidskraft, maskinoppdrag og det som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
▼ −61 %
Operating profit
NOK −1,000
▼ −122 %
Equity
NOK 6,000
▼ −18 %
Est. value
NOK 5,000

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
-8.2%
Not satisfactory
Return on total assets
Solidity
39.0%
Weak
Equity as a share of total capital

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

Who owns GSG MASKIN AS?

GSG MASKIN AS
NOK 6,000 rev. · NOK −1,000 profit

GSG MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GSG MASKIN AS

Who owns GSG MASKIN AS?

Gustav Solum Galguften is the largest registered owner, with 100.0%.

What is the revenue of GSG MASKIN AS?

GSG MASKIN AS had revenue of NOK 6,000 in 2025.

Who is the general manager of GSG MASKIN AS?

Gustav Solum Galguften is registered as general manager of GSG MASKIN AS.

Where is GSG MASKIN AS based?

GSG MASKIN AS has its business address in Overhalla.

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

Report a problem

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