biztrac. BETA
COMPANY REGISTER PROFILE
918036016 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of pleasure boats and equipment

RIGGMASTER AS

Org. no. 918036016 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 154,000
Equity NOK 1.1m
Incorporated 2016
Employees 15
Share capital NOK 40,000

RIGGMASTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918036016. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2016 and has 15 registered employees. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “salg av maritime produkter, herunder men ikke begrenset til riggutstyr, navigasjonsutstyr, tauverk og generelt utstyr til seil- og fritidsbåt, bekledning og sikkerhetsutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 154,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
▼ −12 %
Operating profit
NOK 154,000
▲ +74 %
Equity
NOK 1.1m
▲ +9 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
2.15
Very good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
48.9%
Very good
Equity as a share of total capital

Who owns RIGGMASTER AS?

RIGGMASTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIGGMASTER AS

Who owns RIGGMASTER AS?

Emil Pedersen Hestflått is the largest registered owner, with 50.0%.

What is the revenue of RIGGMASTER AS?

RIGGMASTER AS had revenue of NOK 6.6m in 2025.

Who is the general manager of RIGGMASTER AS?

Tor Kjetil Pedersen is registered as general manager of RIGGMASTER AS.

Where is RIGGMASTER AS based?

RIGGMASTER 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 03.10.2026.

Report a problem

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