BIZTRAC BETA
Machining of metals

AASE GNIST AS

Org. no. 912399966 Limited company (AS) Klepp Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 14.0m
Operating profit NOK 5.4m
Equity NOK 4.9m
Incorporated 2013
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AASE GNIST AS is registered as a limited company in Klepp, Rogaland with organisation number 912399966. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2013. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Bearbeiding av metaller, og hva hermed står i naturlig forbindelse, samt deltakelse av enhver art i andre forretningsforetagende, kjøp og salg av fast eiendom og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.0m in revenue and NOK 5.4m in operating profit.

Key figures · 2025

Revenue
NOK 14.0m
Operating profit
NOK 5.4m
Equity
NOK 4.9m
Est. value
NOK 18.9m

Financial health · 2025

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

Who owns AASE GNIST AS?

MAGNUS AASE AS
AASE GNIST AS
NOK 14.0m rev. · NOK 5.4m profit

AASE GNIST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AASE GNIST AS

Who owns AASE GNIST AS?

MAGNUS AASE AS is the largest registered owner, with 60.0%.

What is the revenue of AASE GNIST AS?

AASE GNIST AS had revenue of NOK 14.0m in 2025.

Who is the general manager of AASE GNIST AS?

Even Magnus Aase is registered as general manager of AASE GNIST AS.

Where is AASE GNIST AS based?

AASE GNIST AS has its business address in Klepp Stasjon.

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.