BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

OSLO GJERDE AS

Org. no. 921632207 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 27,000
Equity NOK 195,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-26 Adresseendring registrert 2026-02-26.

OSLO GJERDE AS is registered as a limited company in Oslo, Oslo with organisation number 921632207. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg og montering av rekkverk, gjerder, trapper og tilhørende produkter og tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 27,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 27,000
Equity
NOK 195,000
Est. value
NOK 219,000

Financial health · 2024

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

Who owns OSLO GJERDE AS?

RUTHEESHAN YOGASUNDARAM
OSLO GJERDE AS
NOK 2.9m rev. · NOK 27,000 profit

OSLO GJERDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO GJERDE AS

Who owns OSLO GJERDE AS?

RUTHEESHAN YOGASUNDARAM is the largest registered owner, with 100.0%.

What is the revenue of OSLO GJERDE AS?

OSLO GJERDE AS had revenue of NOK 2.9m in 2024.

Who is the general manager of OSLO GJERDE AS?

Rutheeshan Yogasundaram is registered as general manager of OSLO GJERDE AS.

Where is OSLO GJERDE AS based?

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