BIZTRAC BETA
Rental and operating of own or leased real estate

SKJÆRINGA 11 AS

Org. no. 919177896 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 9,000
Operating profit NOK −1.6m
Equity NOK 261,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

SKJÆRINGA 11 AS is registered as a limited company in Bærum, Akershus with organisation number 919177896. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 9,000 in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 9,000
Operating profit
NOK −1.6m
Equity
NOK 261,000
Est. value
NOK 192,000

Financial health · 2024

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

Who owns SKJÆRINGA 11 AS?

ANTARCTIC INVEST AS
SKJÆRINGA 11 AS
NOK 9,000 rev. · NOK −1.6m profit

SKJÆRINGA 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKJÆRINGA 11 AS

Who owns SKJÆRINGA 11 AS?

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

What is the revenue of SKJÆRINGA 11 AS?

SKJÆRINGA 11 AS had revenue of NOK 9,000 in 2024.

Where is SKJÆRINGA 11 AS based?

SKJÆRINGA 11 AS has its business address in Lysaker.

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.