biztrac. BETA
COMPANY REGISTER PROFILE
936887759 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

FLAMME AEROSPACE AS

Org. no. 936887759 Limited company (AS) Trondheim Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-15.

FLAMME AEROSPACE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936887759. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og produksjon av rakettmotorer for bruk innen romfart.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 38,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FLAMME AEROSPACE AS?

FLAMME AEROSPACE AS
NOK 0 rev. · NOK 0 profit

FLAMME AEROSPACE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLAMME AEROSPACE AS

Who owns FLAMME AEROSPACE AS?

Ask Haugerud Hovik is the largest registered owner, with 100.0%.

What is the revenue of FLAMME AEROSPACE AS?

FLAMME AEROSPACE AS had revenue of NOK 0 in 2025.

Who is the general manager of FLAMME AEROSPACE AS?

Ask Haugerud Hovik is registered as general manager of FLAMME AEROSPACE AS.

Where is FLAMME AEROSPACE AS based?

FLAMME AEROSPACE 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 03.10.2026.

Report a problem

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