BIZTRAC BETA
Dental practice care activities

TANNLEGE ÅDEL SEKKELSTEN DALE AS

Org. no. 833707612 Limited company (AS) Fredrikstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 208,000
Equity NOK 184,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-13 Avregistrert registrert 2026-06-13.

TANNLEGE ÅDEL SEKKELSTEN DALE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 833707612. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fremstilling/salg av tannlegetjenester og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 208,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 208,000
Equity
NOK 184,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns TANNLEGE ÅDEL SEKKELSTEN DALE AS?

ÅDEL SEKKELSTEN DALE
TANNLEGE ÅDEL SEKKELSTEN DALE AS
NOK 3.1m rev. · NOK 208,000 profit

TANNLEGE ÅDEL SEKKELSTEN DALE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE ÅDEL SEKKELSTEN DALE AS

Who owns TANNLEGE ÅDEL SEKKELSTEN DALE AS?

ÅDEL SEKKELSTEN DALE is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE ÅDEL SEKKELSTEN DALE AS?

TANNLEGE ÅDEL SEKKELSTEN DALE AS had revenue of NOK 3.1m in 2025.

Where is TANNLEGE ÅDEL SEKKELSTEN DALE AS based?

TANNLEGE ÅDEL SEKKELSTEN DALE AS has its business address in Fredrikstad.

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.