BIZTRAC BETA
Site preparation

G O MOLDSKRED AS

Org. no. 911771128 Limited company (AS) Ulstein Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 528,000
Operating profit NOK −248,000
Equity NOK 326,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

G O MOLDSKRED AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 911771128. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørtjenester, leiekjøring og annen beslektet virksomhet herunder kjøp og salg av varer. Selskapet skal kunne delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 528,000 in revenue and NOK −248,000 in operating profit.

Key figures · 2025

Revenue
NOK 528,000
Operating profit
NOK −248,000
Equity
NOK 326,000
Est. value
NOK 324,000

Financial health · 2025

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

Who owns G O MOLDSKRED AS?

GEIR OVE MOLDSKRED
G O MOLDSKRED AS
NOK 528,000 rev. · NOK −248,000 profit

G O MOLDSKRED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about G O MOLDSKRED AS

Who owns G O MOLDSKRED AS?

GEIR OVE MOLDSKRED is the largest registered owner, with 100.0%.

What is the revenue of G O MOLDSKRED AS?

G O MOLDSKRED AS had revenue of NOK 528,000 in 2025.

Who is the general manager of G O MOLDSKRED AS?

Geir Ove Moldskred is registered as general manager of G O MOLDSKRED AS.

Where is G O MOLDSKRED AS based?

G O MOLDSKRED AS has its business address in Haddal.

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.