BIZTRAC BETA
Buying and selling of own real estate

OSLO BYGGFORETAK AS

Org. no. 980623203 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 18,000
Operating profit NOK 13,000
Equity NOK 295,000
Incorporated 1998
Share capital NOK 30,000

Signals

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

OSLO BYGGFORETAK AS is registered as a limited company in Oslo, Oslo with organisation number 980623203. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1998. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 18,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 18,000
Operating profit
NOK 13,000
Equity
NOK 295,000
Est. value
NOK 236,000

Financial health · 2025

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

Who owns OSLO BYGGFORETAK AS?

LEATHERMAN HOLDING AS
OSLO BYGGFORETAK AS
NOK 18,000 rev. · NOK 13,000 profit

OSLO BYGGFORETAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BYGGFORETAK AS

Who owns OSLO BYGGFORETAK AS?

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

What is the revenue of OSLO BYGGFORETAK AS?

OSLO BYGGFORETAK AS had revenue of NOK 18,000 in 2025.

Who is the general manager of OSLO BYGGFORETAK AS?

Satinder Vir Singh is registered as general manager of OSLO BYGGFORETAK AS.

Where is OSLO BYGGFORETAK AS based?

OSLO BYGGFORETAK 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.