BIZTRAC BETA
Manufacture of furniture

CONCORD INTERIØR AS

Org. no. 981439449 Limited company (AS) Trondheim Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 8.0m
Operating profit NOK −2.5m
Equity NOK 30.4m
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,5 mill kr).

CONCORD INTERIØR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 981439449. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel og produksjon og hva som står i forbindelse, herunder deltakelse i annen virksomhet med aksjebesittelse og på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.0m in revenue and NOK −2.5m in operating profit.

Key figures · 2025

Revenue
NOK 8.0m
Operating profit
NOK −2.5m
Equity
NOK 30.4m
Est. value
NOK 22.6m

Financial health · 2025

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

Who owns CONCORD INTERIØR AS?

STIG ARNTSBERG
CONCORD INTERIØR AS
NOK 8.0m rev. · NOK −2.5m profit

CONCORD INTERIØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CONCORD INTERIØR AS own?

CONCORD INTERIØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CONCORD INTERIØR AS

Who owns CONCORD INTERIØR AS?

STIG ARNTSBERG is the largest registered owner, with 100.0%.

What is the revenue of CONCORD INTERIØR AS?

CONCORD INTERIØR AS had revenue of NOK 8.0m in 2025.

Where is CONCORD INTERIØR AS based?

CONCORD INTERIØR AS has its business address in Trondheim.

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.