BIZTRAC BETA
Other technical consultancy

MAGNOR RIGGERTEAM AS

Org. no. 922413622 Limited company (AS) Eidskog Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 170,000
Operating profit NOK −442,000
Equity NOK 319,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

MAGNOR RIGGERTEAM AS is registered as a limited company in Eidskog, Innlandet with organisation number 922413622. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Virksomheten skal drive rådgivning,bemanning og transport for On/Offshore industri.”. The most recent filed accounts, for the 2024 financial year, show NOK 170,000 in revenue and NOK −442,000 in operating profit.

Key figures · 2024

Revenue
NOK 170,000
Operating profit
NOK −442,000
Equity
NOK 319,000
Est. value
NOK 334,000

Financial health · 2024

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

Who owns MAGNOR RIGGERTEAM AS?

HENNING MONSEN
MAGNOR RIGGERTEAM AS
NOK 170,000 rev. · NOK −442,000 profit

MAGNOR RIGGERTEAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAGNOR RIGGERTEAM AS

Who owns MAGNOR RIGGERTEAM AS?

HENNING MONSEN is the largest registered owner, with 100.0%.

What is the revenue of MAGNOR RIGGERTEAM AS?

MAGNOR RIGGERTEAM AS had revenue of NOK 170,000 in 2024.

Who is the general manager of MAGNOR RIGGERTEAM AS?

Henning Monsen is registered as general manager of MAGNOR RIGGERTEAM AS.

Where is MAGNOR RIGGERTEAM AS based?

MAGNOR RIGGERTEAM AS has its business address in Magnor.

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.