biztrac. BETA
COMPANY REGISTER PROFILE
935329124 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

BEDROCK HOLDING AS

Org. no. 935329124 Limited company (AS) Oppdal Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −60,000
Equity NOK 1.0m
Incorporated 2025
Share capital NOK 31,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).

BEDROCK HOLDING AS is registered as a limited company in Oppdal, Trøndelag with organisation number 935329124. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 31,000, divided into 500 shares. The company's stated purpose is: “Investerings- og holdingselskap, med alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −60,000
Equity
NOK 1.0m
Est. value
NOK 501,000

Financial health · 2025

Liquidity
–
Not available
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 BEDROCK HOLDING AS?

BEDROCK HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BEDROCK HOLDING AS own?

BEDROCK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BEDROCK HOLDING AS

Who owns BEDROCK HOLDING AS?

Frank Vognild is the largest registered owner, with 20.0%.

What is the revenue of BEDROCK HOLDING AS?

BEDROCK HOLDING AS had revenue of NOK 0 in 2025.

Where is BEDROCK HOLDING AS based?

BEDROCK HOLDING AS has its business address in Oppdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.