BIZTRAC BETA
Electrical installation

MARITIM-ELEKTRO AS

Org. no. 920382665 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 979,000
Operating profit NOK −71,000
Equity NOK 1.1m
Incorporated 2018
Share capital NOK 30,000

Signals

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

MARITIM-ELEKTRO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920382665. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Teknisk skipselektro, skipselektronikk, reparasjon og forandringer i elektriske anlegg, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 979,000 in revenue and NOK −71,000 in operating profit.

Key figures · 2025

Revenue
NOK 979,000
Operating profit
NOK −71,000
Equity
NOK 1.1m
Est. value
NOK 809,000

Financial health · 2025

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

Who owns MARITIM-ELEKTRO AS?

STEVE TORBJØRN PEDERSEN
MARITIM-ELEKTRO AS
NOK 979,000 rev. · NOK −71,000 profit

MARITIM-ELEKTRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MARITIM-ELEKTRO AS

Who owns MARITIM-ELEKTRO AS?

STEVE TORBJØRN PEDERSEN is the largest registered owner, with 90.0%.

What is the revenue of MARITIM-ELEKTRO AS?

MARITIM-ELEKTRO AS had revenue of NOK 979,000 in 2025.

Who is the general manager of MARITIM-ELEKTRO AS?

Steve Torbjørn Pedersen is registered as general manager of MARITIM-ELEKTRO AS.

Where is MARITIM-ELEKTRO AS based?

MARITIM-ELEKTRO AS has its business address in Klæbu.

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.