BIZTRAC BETA
Retail sale of automotive fuel

NIINGSKROA AS

Org. no. 990440344 Limited company (AS) Evenes Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 279,000
Equity NOK 2.2m
Incorporated 2006
Employees 19
Share capital NOK 200,000

NIINGSKROA AS is registered as a limited company in Evenes, Nordland with organisation number 990440344. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2006 and has 19 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drift av bensinstasjon med tilhørende kafe samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 279,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 279,000
Equity
NOK 2.2m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns NIINGSKROA AS?

HANS JOHNNY HILMON NILSSEN
NIINGSKROA AS
NOK 6.9m rev. · NOK 279,000 profit

NIINGSKROA AS has 6 registered shareholders:

All shareholders and roles →

Which companies does NIINGSKROA AS own?

NIINGSKROA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NIINGSKROA AS

Who owns NIINGSKROA AS?

HANS JOHNNY HILMON NILSSEN is the largest registered owner, with 40.0%.

What is the revenue of NIINGSKROA AS?

NIINGSKROA AS had revenue of NOK 6.9m in 2025.

Who is the general manager of NIINGSKROA AS?

Monica Oddrun Nilssen is registered as general manager of NIINGSKROA AS.

Where is NIINGSKROA AS based?

NIINGSKROA AS has its business address in Bogen I Ofoten.

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.