biztrac. BETA
COMPANY REGISTER PROFILE
928195163 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Dental practice care activities

NYTT SMIL AS

Org. no. 928195163 Limited company (AS) Oslo Incorporated 2021 Active
Revenue 2025 NOK 135,000
Operating profit NOK 80,000
Equity NOK 83,000
Incorporated 2021
Share capital NOK 30,000

NYTT SMIL AS is registered as a limited company in Oslo, Oslo with organisation number 928195163. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby tannlegetjenester til privatmarkedet og delta i forretningsområder beslektet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 135,000 in revenue and NOK 80,000 in operating profit.

Key figures · 2025

Revenue
NOK 135,000
▼ −6 %
Operating profit
NOK 80,000
▲ +248 %
Equity
NOK 83,000
▲ +286 %
Est. value
NOK 170,000

Financial health · 2025

Liquidity
13.63
Very good
Current assets ÷ current liabilities
Profitability
130.9%
Very good
Return on total assets
Solidity
92.7%
Weak
Equity as a share of total capital

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

Who owns NYTT SMIL AS?

SOLDENT HUNGARY KFT. HU
NYTT SMIL AS
NOK 135,000 rev. · NOK 80,000 profit

NYTT SMIL AS has 1 registered shareholder:

  • SOLDENT HUNGARY KFT. 100.0%
All shareholders and roles →

Frequently asked questions about NYTT SMIL AS

Who owns NYTT SMIL AS?

SOLDENT HUNGARY KFT. is the largest registered owner, with 100.0%.

What is the revenue of NYTT SMIL AS?

NYTT SMIL AS had revenue of NOK 135,000 in 2025.

Who is the general manager of NYTT SMIL AS?

Zoltan Olah is registered as general manager of NYTT SMIL AS.

Where is NYTT SMIL AS based?

NYTT SMIL 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 03.10.2026.

Report a problem

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