BIZTRAC BETA
Civil engineering activities

OLAV BRUNBORGS VEI 13 AS

Org. no. 936708021 Limited company (AS) Oslo Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 376,000
Operating profit NOK 24,000
Equity NOK 347,000
Incorporated 1985
Share capital NOK 100,000

Signals

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

OLAV BRUNBORGS VEI 13 AS is registered as a limited company in Oslo, Oslo with organisation number 936708021. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1985. Registered share capital is NOK 100,000. The company's stated purpose is: “Erverve og leie ut fast eiendom samt hva hermed står i forbindelse, herunder delta i andre sel- skaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 376,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 376,000
Operating profit
NOK 24,000
Equity
NOK 347,000
Est. value
NOK 346,000

Financial health · 2025

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

Who owns OLAV BRUNBORGS VEI 13 AS?

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS
OLAV BRUNBORGS VEI 13 AS
NOK 376,000 rev. · NOK 24,000 profit

OLAV BRUNBORGS VEI 13 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAV BRUNBORGS VEI 13 AS

Who owns OLAV BRUNBORGS VEI 13 AS?

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS is the largest registered owner, with 100.0%.

What is the revenue of OLAV BRUNBORGS VEI 13 AS?

OLAV BRUNBORGS VEI 13 AS had revenue of NOK 376,000 in 2025.

Where is OLAV BRUNBORGS VEI 13 AS based?

OLAV BRUNBORGS VEI 13 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.