BIZTRAC BETA
Rental and operating of own or leased real estate

SKJEBERG SENTER AS

Org. no. 986813659 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 2.5m
Equity NOK 30.0m
Incorporated 2004
Share capital NOK 30.0m

SKJEBERG SENTER AS is registered as a limited company in Oslo, Oslo with organisation number 986813659. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 30.0m, divided into 120 shares. The company's stated purpose is: “Kjøp, forvaltning, utvikling og utleie av fast eiendom, samt å drive virksomhet 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 foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 2.5m
Equity
NOK 30.0m
Est. value
NOK 27.3m

Financial health · 2024

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

Who owns SKJEBERG SENTER AS?

BIL INVEST OSLO AS
SKJEBERG SENTER AS
NOK 4.3m rev. · NOK 2.5m profit

SKJEBERG SENTER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SKJEBERG SENTER AS er morselskap for 3 datterselskaper:

Frequently asked questions about SKJEBERG SENTER AS

Who owns SKJEBERG SENTER AS?

BIL INVEST OSLO AS is the largest registered owner, with 100.0%.

What is the revenue of SKJEBERG SENTER AS?

SKJEBERG SENTER AS had revenue of NOK 4.3m in 2024.

Where is SKJEBERG SENTER AS based?

SKJEBERG SENTER 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.