BIZTRAC BETA
General cleaning of buildings

OSEBERG MILJØ AS

Org. no. 913507487 Limited company (AS) Tønsberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 348,000
Equity NOK 606,000
Incorporated 2014
Employees 16
Share capital NOK 100,000

OSEBERG MILJØ AS is registered as a limited company in Tønsberg, Vestfold with organisation number 913507487. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2014 and has 16 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av rengjøringsbyrå etter moderne metoder og hva som dermed står i forbindelse for et bedre miljø, samt handel og utleie, ervervelse av fast eiendom og deltagelse i annen virksomhet med økonomiske formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 348,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK 348,000
Equity
NOK 606,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.4%
Good
Equity as a share of total capital

Who owns OSEBERG MILJØ AS?

ROLAND PETTERSEN
OSEBERG MILJØ AS
NOK 5.5m rev. · NOK 348,000 profit

OSEBERG MILJØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSEBERG MILJØ AS

Who owns OSEBERG MILJØ AS?

ROLAND PETTERSEN is the largest registered owner, with 90.0%.

What is the revenue of OSEBERG MILJØ AS?

OSEBERG MILJØ AS had revenue of NOK 5.5m in 2025.

Who is the general manager of OSEBERG MILJØ AS?

Roland Pettersen is registered as general manager of OSEBERG MILJØ AS.

Where is OSEBERG MILJØ AS based?

OSEBERG MILJØ AS has its business address in Tønsberg.

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.