biztrac. BETA
COMPANY REGISTER PROFILE
919567295 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Non-specialised wholesale trade

STILI PROFIL AS

Org. no. 919567295 Limited company (AS) Øystre Slidre Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 38,000
Equity NOK 264,000
Incorporated 2017
Share capital NOK 30,000

STILI PROFIL AS is registered as a limited company in Øystre Slidre, Innlandet with organisation number 919567295. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av profilartikler og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +40 %
Operating profit
NOK 38,000
▲ +74 %
Equity
NOK 264,000
▲ +8 %
Est. value
NOK 240,000

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
7.4%
Satisfactory
Return on total assets
Solidity
35.9%
Good
Equity as a share of total capital

Who owns STILI PROFIL AS?

STILI PROFIL AS
NOK 2.7m rev. · NOK 38,000 profit

STILI PROFIL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STILI PROFIL AS

Who owns STILI PROFIL AS?

Brede Udahl is the largest registered owner, with 50.0%.

What is the revenue of STILI PROFIL AS?

STILI PROFIL AS had revenue of NOK 2.7m in 2025.

Who is the general manager of STILI PROFIL AS?

Brede Udahl is registered as general manager of STILI PROFIL AS.

Where is STILI PROFIL AS based?

STILI PROFIL AS has its business address in Beito.

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.