BIZTRAC BETA
Dental practice care activities

F. BRUVIK AS

Org. no. 931622870 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 18,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

F. BRUVIK AS is registered as a limited company in Bergen, Vestland with organisation number 931622870. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer og andre virksomheter, herunder kjøp og salg av fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 18,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns F. BRUVIK AS?

FRIDA CORNELIA BRUVIK FORLAND
F. BRUVIK AS
NOK 0 rev. · NOK −3,000 profit

F. BRUVIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does F. BRUVIK AS own?

F. BRUVIK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about F. BRUVIK AS

Who owns F. BRUVIK AS?

FRIDA CORNELIA BRUVIK FORLAND is the largest registered owner, with 100.0%.

What is the revenue of F. BRUVIK AS?

F. BRUVIK AS had revenue of NOK 0 in 2025.

Where is F. BRUVIK AS based?

F. BRUVIK AS has its business address in Bergen.

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.