BIZTRAC BETA
Uoppgitt

BEDROCK INVEST AS

Org. no. 936671527 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −216
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−216 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-03.

BEDROCK INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 936671527. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −216 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −216
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BEDROCK INVEST AS?

KENT OVE RØNNING VALØ
BEDROCK INVEST AS
NOK 0 rev. · NOK −216 profit

BEDROCK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEDROCK INVEST AS

Who owns BEDROCK INVEST AS?

KENT OVE RØNNING VALØ is the largest registered owner, with 100.0%.

What is the revenue of BEDROCK INVEST AS?

BEDROCK INVEST AS had revenue of NOK 0 in 2025.

Where is BEDROCK INVEST AS based?

BEDROCK INVEST 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.