BIZTRAC BETA
Uoppgitt

SEBESTØDEL AS

Org. no. 926906534 Limited company (AS) Karmøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK −183,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−183k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

SEBESTØDEL AS is registered as a limited company in Karmøy, Rogaland with organisation number 926906534. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapirer og enkeltaksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK −183,000

Financial health · 2025

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.9%
Weak
Equity as a share of total capital

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

Who owns SEBESTØDEL AS?

RAGNAR LANGÅKER
SEBESTØDEL AS
NOK 0 rev. · NOK −1,000 profit

SEBESTØDEL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEBESTØDEL AS own?

SEBESTØDEL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEBESTØDEL AS

Who owns SEBESTØDEL AS?

RAGNAR LANGÅKER is the largest registered owner, with 100.0%.

What is the revenue of SEBESTØDEL AS?

SEBESTØDEL AS had revenue of NOK 0 in 2025.

Who is the general manager of SEBESTØDEL AS?

Ragnar Langåker is registered as general manager of SEBESTØDEL AS.

Where is SEBESTØDEL AS based?

SEBESTØDEL AS has its business address in Stol.

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.