biztrac. BETA
COMPANY REGISTER PROFILE
994273728 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Manufacture of non-domestic air conditioning equipment

AER FABER AS

Org. no. 994273728 Limited company (AS) Indre Østfold Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 72.0m
Operating profit NOK 12.5m
Equity NOK 19.9m
Incorporated 2009
Employees 25
Share capital NOK 100,000

AER FABER AS is registered as a limited company in Indre Østfold, Østfold with organisation number 994273728. The business is classified under manufacture of non-domestic air conditioning equipment (NACE 28.250). The company was incorporated in 2009 and has 25 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og salg av ventilasjonsutstyr og annet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 72.0m in revenue and NOK 12.5m in operating profit.

Former names: AERFA AS

Key figures · 2025

Revenue
NOK 72.0m
▼ −9 %
Operating profit
NOK 12.5m
▼ −16 %
Equity
NOK 19.9m
▼ −18 %
Est. value
NOK 53.9m

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
31.0%
Very good
Return on total assets
Solidity
45.2%
Very good
Equity as a share of total capital

Who owns AER FABER AS?

AER FABER AS
NOK 72.0m rev. · NOK 12.5m profit

AER FABER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AER FABER AS

Who owns AER FABER AS?

Lindab A/S is the largest registered owner, with 100.0%.

What is the revenue of AER FABER AS?

AER FABER AS had revenue of NOK 72.0m in 2025.

Who is the general manager of AER FABER AS?

Erik Iversen is registered as general manager of AER FABER AS.

Where is AER FABER AS based?

AER FABER AS has its business address in Spydeberg.

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.