BIZTRAC BETA
Other support activities to arts and performing arts

FLIGHTCASE BY SKARDING AS

Org. no. 925414042 Limited company (AS) Bjørnafjorden Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 52,000
Equity NOK 169,000
Incorporated 2020
Share capital NOK 112,000

FLIGHTCASE BY SKARDING AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 925414042. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2020. Registered share capital is NOK 112,000, divided into 112 shares. The company's stated purpose is: “Salg og produksjon av produkter til musikkbransjen (backline).”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 52,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 52,000
Equity
NOK 169,000
Est. value
NOK 222,000

Financial health · 2024

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.9%
Good
Equity as a share of total capital

Who owns FLIGHTCASE BY SKARDING AS?

HÅKON SKULSTAD SKARDING
FLIGHTCASE BY SKARDING AS
NOK 4.6m rev. · NOK 52,000 profit

FLIGHTCASE BY SKARDING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLIGHTCASE BY SKARDING AS

Who owns FLIGHTCASE BY SKARDING AS?

HÅKON SKULSTAD SKARDING is the largest registered owner, with 50.9%.

What is the revenue of FLIGHTCASE BY SKARDING AS?

FLIGHTCASE BY SKARDING AS had revenue of NOK 4.6m in 2024.

Who is the general manager of FLIGHTCASE BY SKARDING AS?

Håkon Skulstad Skarding is registered as general manager of FLIGHTCASE BY SKARDING AS.

Where is FLIGHTCASE BY SKARDING AS based?

FLIGHTCASE BY SKARDING AS has its business address in Hagavik.

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.