BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

SOJAMA MARITIME SUPPORT AS

Org. no. 923457143 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 6,000
Equity NOK 30,000
Incorporated 2019
Share capital NOK 30,000

SOJAMA MARITIME SUPPORT AS is registered as a limited company in Stavanger, Rogaland with organisation number 923457143. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med utleie av arbeidskraft, i tillegg til salg av utstyr for marine, Wind og offshore næringen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 6,000
Equity
NOK 30,000
Est. value
NOK 41,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SOJAMA MARITIME SUPPORT AS?

FINN-MARTIN NILSEN
SOJAMA MARITIME SUPPORT AS
NOK 1.6m rev. · NOK 6,000 profit

SOJAMA MARITIME SUPPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOJAMA MARITIME SUPPORT AS

Who owns SOJAMA MARITIME SUPPORT AS?

FINN-MARTIN NILSEN is the largest registered owner, with 100.0%.

What is the revenue of SOJAMA MARITIME SUPPORT AS?

SOJAMA MARITIME SUPPORT AS had revenue of NOK 1.6m in 2025.

Where is SOJAMA MARITIME SUPPORT AS based?

SOJAMA MARITIME SUPPORT AS has its business address in Stavanger.

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.