BIZTRAC BETA
Joinery installation

OSLO BYGG OG VAKTMESTERTJENESTER AS

Org. no. 931019546 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 432,000
Equity NOK 259,000
Incorporated 2023
Share capital NOK 30,000

OSLO BYGG OG VAKTMESTERTJENESTER AS is registered as a limited company in Oslo, Oslo with organisation number 931019546. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørtjenester innenfor bygg, anlegg og vaktmestertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 432,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 432,000
Equity
NOK 259,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns OSLO BYGG OG VAKTMESTERTJENESTER AS?

INVEST1N AS
OSLO BYGG OG VAKTMESTERTJENESTER AS
NOK 1.2m rev. · NOK 432,000 profit

OSLO BYGG OG VAKTMESTERTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BYGG OG VAKTMESTERTJENESTER AS

Who owns OSLO BYGG OG VAKTMESTERTJENESTER AS?

INVEST1N AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO BYGG OG VAKTMESTERTJENESTER AS?

OSLO BYGG OG VAKTMESTERTJENESTER AS had revenue of NOK 1.2m in 2025.

Who is the general manager of OSLO BYGG OG VAKTMESTERTJENESTER AS?

Metin Øzbek is registered as general manager of OSLO BYGG OG VAKTMESTERTJENESTER AS.

Where is OSLO BYGG OG VAKTMESTERTJENESTER AS based?

OSLO BYGG OG VAKTMESTERTJENESTER 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.