BIZTRAC BETA
Dental practice care activities

BOGSTADVEIEN TANNLEGEKONTOR AS

Org. no. 986804579 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 83,000
Equity NOK 661,000
Incorporated 2004
Share capital NOK 100,000

BOGSTADVEIEN TANNLEGEKONTOR AS is registered as a limited company in Oslo, Oslo with organisation number 986804579. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av tannlegekontor med tannlegebehandling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 83,000
Equity
NOK 661,000
Est. value
NOK 898,000

Financial health · 2025

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

Who owns BOGSTADVEIEN TANNLEGEKONTOR AS?

CHRISTER VILHELM RANFELT
BOGSTADVEIEN TANNLEGEKONTOR AS
NOK 1.9m rev. · NOK 83,000 profit

BOGSTADVEIEN TANNLEGEKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOGSTADVEIEN TANNLEGEKONTOR AS

Who owns BOGSTADVEIEN TANNLEGEKONTOR AS?

CHRISTER VILHELM RANFELT is the largest registered owner, with 100.0%.

What is the revenue of BOGSTADVEIEN TANNLEGEKONTOR AS?

BOGSTADVEIEN TANNLEGEKONTOR AS had revenue of NOK 1.9m in 2025.

Who is the general manager of BOGSTADVEIEN TANNLEGEKONTOR AS?

Christer Vilhelm Ranfelt is registered as general manager of BOGSTADVEIEN TANNLEGEKONTOR AS.

Where is BOGSTADVEIEN TANNLEGEKONTOR AS based?

BOGSTADVEIEN TANNLEGEKONTOR 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.