BIZTRAC BETA
Washing and cleaning of textile and fur products

A B MATTESERVICE AS

Org. no. 974493411 Limited company (AS) Asker Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 20.4m
Operating profit NOK 751,000
Equity NOK 685,000
Incorporated 1995
Employees 22
Share capital NOK 112,000

A B MATTESERVICE AS is registered as a limited company in Asker, Akershus with organisation number 974493411. The business is classified under washing and cleaning of textile and fur products (NACE 96.100). The company was incorporated in 1995 and has 22 registered employees. Registered share capital is NOK 112,000, divided into 50 shares. The company's stated purpose is: “Drive mattevaskeri, handel, herunder import og eksport. Videre skal selskapet kunne erverve fast eiendom, samt stå for driften av slike. ”. The most recent filed accounts, for the 2025 financial year, show NOK 20.4m in revenue and NOK 751,000 in operating profit.

Key figures · 2025

Revenue
NOK 20.4m
Operating profit
NOK 751,000
Equity
NOK 685,000
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns A B MATTESERVICE AS?

ADAMSTUEN HOLDING AS
A B MATTESERVICE AS
NOK 20.4m rev. · NOK 751,000 profit

A B MATTESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A B MATTESERVICE AS

Who owns A B MATTESERVICE AS?

ADAMSTUEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of A B MATTESERVICE AS?

A B MATTESERVICE AS had revenue of NOK 20.4m in 2025.

Who is the general manager of A B MATTESERVICE AS?

Rajah Vadivelu is registered as general manager of A B MATTESERVICE AS.

Where is A B MATTESERVICE AS based?

A B MATTESERVICE AS has its business address in Asker.

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.