BIZTRAC BETA
Finishing of textiles

DIN PROFILTJENESTE AS

Org. no. 931803115 Limited company (AS) Færder Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 825,000
Operating profit NOK 7,000
Equity NOK 139,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-05 Adresseendring registrert 2026-06-05.

DIN PROFILTJENESTE AS is registered as a limited company in Færder, Vestfold with organisation number 931803115. The business is classified under finishing of textiles (NACE 13.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Foliedekor, solfilm, profilering og trykking av klær samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 825,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 825,000
Operating profit
NOK 7,000
Equity
NOK 139,000
Est. value
NOK 106,000

Financial health · 2025

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

Who owns DIN PROFILTJENESTE AS?

BERAT MEXHUANI
DIN PROFILTJENESTE AS
NOK 825,000 rev. · NOK 7,000 profit

DIN PROFILTJENESTE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIN PROFILTJENESTE AS

Who owns DIN PROFILTJENESTE AS?

BERAT MEXHUANI is the largest registered owner, with 100.0%.

What is the revenue of DIN PROFILTJENESTE AS?

DIN PROFILTJENESTE AS had revenue of NOK 825,000 in 2025.

Who is the general manager of DIN PROFILTJENESTE AS?

Berat Mexhuani is registered as general manager of DIN PROFILTJENESTE AS.

Where is DIN PROFILTJENESTE AS based?

DIN PROFILTJENESTE AS has its business address in Kjøpmannskjær.

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.