BIZTRAC BETA
Business and other management consultancy activities

SFL ETS AS

Org. no. 933705048 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 20,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SFL ETS AS is registered as a limited company in Oslo, Oslo with organisation number 933705048. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, leie inn og/eller leie ut skip og for øvrig drive maritim virksomhet og annen virksomhet som står i forbindelse dermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 20,000
Est. value
NOK 33,000

Financial health · 2025

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

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

Who owns SFL ETS AS?

SFL MANAGEMENT BERMUDA LTD
SFL ETS AS
NOK 0 rev. · NOK −3,000 profit

SFL ETS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SFL ETS AS

Who owns SFL ETS AS?

SFL MANAGEMENT BERMUDA LTD is the largest registered owner, with 100.0%.

What is the revenue of SFL ETS AS?

SFL ETS AS had revenue of NOK 0 in 2025.

Where is SFL ETS AS based?

SFL ETS AS has its business address in Oslo.

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.