BIZTRAC BETA
Rental and operating of own or leased real estate

OSEBERG INVEST AS

Org. no. 980283550 Limited company (AS) Drammen Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 1.8m
Equity NOK 8.0m
Incorporated 1998
Share capital NOK 240,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OSEBERG INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 980283550. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 240,000, divided into 1200 shares. The company's stated purpose is: “Utleie av løsøre og fast eiendom. Investering i aksjer og andre verdipapirer samt tomter og annen fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 1.8m
Equity
NOK 8.0m
Est. value
NOK 9.5m

Financial health · 2025

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

Who owns OSEBERG INVEST AS?

BUSKERUD BLIKK HOLDING AS
OSEBERG INVEST AS
NOK 2.4m rev. · NOK 1.8m profit

OSEBERG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OSEBERG INVEST AS er morselskap for 3 datterselskaper:

Frequently asked questions about OSEBERG INVEST AS

Who owns OSEBERG INVEST AS?

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

What is the revenue of OSEBERG INVEST AS?

OSEBERG INVEST AS had revenue of NOK 2.4m in 2025.

Where is OSEBERG INVEST AS based?

OSEBERG INVEST AS has its business address in Drammen.

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.