BIZTRAC BETA
Dental practice care activities

TANNLEGE EGIL SEKKELSTEN AS

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

Signals

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

TANNLEGE EGIL SEKKELSTEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 933706966. 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 63,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 63,000
Equity
NOK 42,000
Est. value
NOK 317,000

Financial health · 2025

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

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

Who owns TANNLEGE EGIL SEKKELSTEN AS?

EGIL SEKKELSTEN
TANNLEGE EGIL SEKKELSTEN AS
NOK 3.1m rev. · NOK 63,000 profit

TANNLEGE EGIL SEKKELSTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE EGIL SEKKELSTEN AS

Who owns TANNLEGE EGIL SEKKELSTEN AS?

EGIL SEKKELSTEN is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE EGIL SEKKELSTEN AS?

TANNLEGE EGIL SEKKELSTEN AS had revenue of NOK 3.1m in 2025.

Where is TANNLEGE EGIL SEKKELSTEN AS based?

TANNLEGE EGIL SEKKELSTEN 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.