biztrac. BETA
COMPANY REGISTER PROFILE
931951556 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

STERTEBAKKE 3 AS

Org. no. 931951556 Limited company (AS) Kongsberg Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −122,000
Equity NOK −558,000
Incorporated 2023
Share capital NOK 76,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−558k kr).

STERTEBAKKE 3 AS is registered as a limited company in Kongsberg, Buskerud with organisation number 931951556. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 76,000, divided into 300 shares. The company's stated purpose is: “Investere i eiendom, boliger, leiligheter mv. for utleie og kjøp og salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −122,000 in operating profit.

Former names: NYE OMNIA EIENDOM AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −122,000
▼ −69 %
Equity
NOK −558,000
▼ −540 %

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.6%
Not satisfactory
Return on total assets
Solidity
-5.2%
Weak
Equity as a share of total capital

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

Who owns STERTEBAKKE 3 AS?

STERTEBAKKE 3 AS
NOK 0 rev. · NOK −122,000 profit

STERTEBAKKE 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STERTEBAKKE 3 AS

Who owns STERTEBAKKE 3 AS?

OMNIA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STERTEBAKKE 3 AS?

STERTEBAKKE 3 AS had revenue of NOK 0 in 2025.

Where is STERTEBAKKE 3 AS based?

STERTEBAKKE 3 AS has its business address in Kongsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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