BIZTRAC BETA
Retail sale of pets and pet food

NOAS ARK AS

Org. no. 912891410 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 138,000
Equity NOK 696,000
Incorporated 2013
Employees 5
Share capital NOK 370,000

NOAS ARK AS is registered as a limited company in Bærum, Akershus with organisation number 912891410. The business is classified under retail sale of pets and pet food (NACE 47.762). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 370,000, divided into 1000 shares. The company's stated purpose is: “Salg av fòr og utstyr til husdyr og aktiviteter rettet mot denne målgruppe, eller på annen måte delta i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 138,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 138,000
Equity
NOK 696,000
Est. value
NOK 896,000

Financial health · 2025

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

Who owns NOAS ARK AS?

AGNES MARIA STØYLEN
NOAS ARK AS
NOK 6.3m rev. · NOK 138,000 profit

NOAS ARK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NOAS ARK AS own?

NOAS ARK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NOAS ARK AS

Who owns NOAS ARK AS?

AGNES MARIA STØYLEN is the largest registered owner, with 100.0%.

What is the revenue of NOAS ARK AS?

NOAS ARK AS had revenue of NOK 6.3m in 2025.

Who is the general manager of NOAS ARK AS?

Agnes Maria Støylen is registered as general manager of NOAS ARK AS.

Where is NOAS ARK AS based?

NOAS ARK AS has its business address in Rykkinn.

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.