BIZTRAC BETA
Repair and maintenance of civilian air and spacecraft

SAM AERO CAPITAL AS

Org. no. 999262201 Limited company (AS) Ullensaker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 741,000
Equity NOK 1.0m
Incorporated 2012
Share capital NOK 129,000

SAM AERO CAPITAL AS is registered as a limited company in Ullensaker, Akershus with organisation number 999262201. The business is classified under repair and maintenance of civilian air and spacecraft (NACE 33.160). The company was incorporated in 2012. Registered share capital is NOK 129,000, divided into 128698 shares. The company's stated purpose is: “Reparasjon og vedlikehold av luftfartøy samt det som naturlig står i forbindelse med dette, herunder deltakelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 741,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 741,000
Equity
NOK 1.0m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns SAM AERO CAPITAL AS?

JAN HUGO HANSEN LIMITED NUF
SAM AERO CAPITAL AS
NOK 3.1m rev. · NOK 741,000 profit

SAM AERO CAPITAL AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAM AERO CAPITAL AS

Who owns SAM AERO CAPITAL AS?

JAN HUGO HANSEN LIMITED NUF is the largest registered owner, with 43.0%.

What is the revenue of SAM AERO CAPITAL AS?

SAM AERO CAPITAL AS had revenue of NOK 3.1m in 2024.

Who is the general manager of SAM AERO CAPITAL AS?

Ole Petter Monsbakken is registered as general manager of SAM AERO CAPITAL AS.

Where is SAM AERO CAPITAL AS based?

SAM AERO CAPITAL AS has its business address in Gardermoen.

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.