BIZTRAC BETA
Uoppgitt

LONGSLEEVE HOLDING AS

Org. no. 930828130 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 60,000
Incorporated 2023
Share capital NOK 110,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

LONGSLEEVE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 930828130. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 110,000, divided into 110000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK 60,000
Est. value
NOK 71,000

Financial health · 2024

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

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

Who owns LONGSLEEVE HOLDING AS?

VEGARD PEDERSEN
LONGSLEEVE HOLDING AS
· NOK −3,000 profit

LONGSLEEVE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LONGSLEEVE HOLDING AS own?

LONGSLEEVE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LONGSLEEVE HOLDING AS

Who owns LONGSLEEVE HOLDING AS?

VEGARD PEDERSEN is the largest registered owner, with 100.0%.

Who is the general manager of LONGSLEEVE HOLDING AS?

Vegard Pedersen is registered as general manager of LONGSLEEVE HOLDING AS.

Where is LONGSLEEVE HOLDING AS based?

LONGSLEEVE HOLDING 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.