BIZTRAC BETA
COMPANY REGISTER PROFILE
997773802 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

MOGOP AS

Org. no. 997773802 Limited company (AS) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 6.7m
Incorporated 2011
Share capital NOK 100,000

Signals

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

MOGOP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 997773802. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og investeringer i eindommer samt alt hva her står i forbeindelse, samt ved aksjetegning eller på annen måte deltaglese i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 6.7m
Est. value
NOK 9.3m

Financial health · 2025

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

Who owns MOGOP AS?

MOGOP AS
NOK 0 rev. · NOK −16,000 profit

MOGOP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOGOP AS

Who owns MOGOP AS?

GEIR SVERRE BELLINGMO is the largest registered owner, with 100.0%.

What is the revenue of MOGOP AS?

MOGOP AS had revenue of NOK 0 in 2025.

Who is the general manager of MOGOP AS?

Geir Sverre Bellingmo is registered as general manager of MOGOP AS.

Where is MOGOP AS based?

MOGOP AS has its business address in Trondheim.

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

Report a problem

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