BIZTRAC BETA
Development of building projects

BREIVIKVEIEN 48 AS

Org. no. 987558733 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 461,000
Incorporated 2004
Share capital NOK 200,000

Signals

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

BREIVIKVEIEN 48 AS is registered as a limited company in Oslo, Oslo with organisation number 987558733. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2004. Registered share capital is NOK 200,000, divided into 1 shares. The company's stated purpose is: “Selskapets formål er å investere i fast eiendom, samt eie, leie ut og på annen måte drive fast eiendom og det som naturlig står i denne forbindelse, samt å investere i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 461,000
Est. value
NOK 316,000

Financial health · 2025

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

Who owns BREIVIKVEIEN 48 AS?

JM NORGE AS
BREIVIKVEIEN 48 AS
NOK 0 rev. · NOK 0 profit

BREIVIKVEIEN 48 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BREIVIKVEIEN 48 AS er morselskap for 5 datterselskaper:

Frequently asked questions about BREIVIKVEIEN 48 AS

Who owns BREIVIKVEIEN 48 AS?

JM NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of BREIVIKVEIEN 48 AS?

BREIVIKVEIEN 48 AS had revenue of NOK 0 in 2025.

Where is BREIVIKVEIEN 48 AS based?

BREIVIKVEIEN 48 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.