BIZTRAC BETA
COMPANY REGISTER PROFILE
936801080 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SKULLERUD INVEST AS

Org. no. 936801080 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 790,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-14.

SKULLERUD INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 936801080. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i selskap, aksjer, verdipapirer, eiendom og finansielle instrumenter, samt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 790,000
Est. value
NOK 928,000

Financial health · 2025

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

Who owns SKULLERUD INVEST AS?

SKULLERUD INVEST AS
NOK 0 rev. · NOK 0 profit

SKULLERUD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKULLERUD INVEST AS own?

SKULLERUD INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKULLERUD INVEST AS

Who owns SKULLERUD INVEST AS?

ARILD ENRIQUEZ SKULLERUD is the largest registered owner, with 100.0%.

What is the revenue of SKULLERUD INVEST AS?

SKULLERUD INVEST AS had revenue of NOK 0 in 2025.

Where is SKULLERUD INVEST AS based?

SKULLERUD INVEST 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 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.