BIZTRAC BETA
COMPANY REGISTER PROFILE
979495536 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Retail sale of carpets, rugs, wall and floor coverings

PARS TEPPER AS

Org. no. 979495536 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 10.5m
Operating profit NOK 817,000
Equity NOK 2.7m
Incorporated 1997
Share capital NOK 100,000

PARS TEPPER AS is registered as a limited company in Oslo, Oslo with organisation number 979495536. The business is classified under retail sale of carpets, rugs, wall and floor coverings (NACE 47.530). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og hva som står i forbindelse med dette. Selskapet kan ved innskudd eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.5m in revenue and NOK 817,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.5m
▲ +2 %
Operating profit
NOK 817,000
▼ −54 %
Equity
NOK 2.7m
▼ −19 %
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
3.14
Very good
Current assets ÷ current liabilities
Profitability
12.4%
Good
Return on total assets
Solidity
45.8%
Very good
Equity as a share of total capital

Who owns PARS TEPPER AS?

PARS TEPPER AS
NOK 10.5m rev. · NOK 817,000 profit

PARS TEPPER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARS TEPPER AS

Who owns PARS TEPPER AS?

PEYMAN MOVAFAGH is the largest registered owner, with 100.0%.

What is the revenue of PARS TEPPER AS?

PARS TEPPER AS had revenue of NOK 10.5m in 2025.

Who is the general manager of PARS TEPPER AS?

Peyman Movafagh is registered as general manager of PARS TEPPER AS.

Where is PARS TEPPER AS based?

PARS TEPPER 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 02.09.2026.

Report a problem

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