BIZTRAC BETA
Repair and maintenance of machinery

PEDERSEN SUBSEA CONSULTING AS

Org. no. 931480588 Limited company (AS) Klepp Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 510,000
Equity NOK 709,000
Incorporated 2023
Share capital NOK 30,000

PEDERSEN SUBSEA CONSULTING AS is registered as a limited company in Klepp, Rogaland with organisation number 931480588. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Reparasjon av maskiner og teknisk konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 510,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 510,000
Equity
NOK 709,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns PEDERSEN SUBSEA CONSULTING AS?

T.PEDERSEN HOLDING AS
PEDERSEN SUBSEA CONSULTING AS
NOK 1.7m rev. · NOK 510,000 profit

PEDERSEN SUBSEA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEDERSEN SUBSEA CONSULTING AS

Who owns PEDERSEN SUBSEA CONSULTING AS?

T.PEDERSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PEDERSEN SUBSEA CONSULTING AS?

PEDERSEN SUBSEA CONSULTING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of PEDERSEN SUBSEA CONSULTING AS?

Trond-Egil Pedersen is registered as general manager of PEDERSEN SUBSEA CONSULTING AS.

Where is PEDERSEN SUBSEA CONSULTING AS based?

PEDERSEN SUBSEA CONSULTING AS has its business address in Kvernaland.

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.