biztrac. BETA
COMPANY REGISTER PROFILE
812668722 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

ATYS AS

Org. no. 812668722 Limited company (AS) Klepp Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 59,000
Operating profit NOK 18,000
Equity NOK 875,000
Incorporated 2013
Share capital NOK 30,000

ATYS AS is registered as a limited company in Klepp, Rogaland with organisation number 812668722. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenester innen data og IT samt det som naturlig står i forbindelse med dette herunder å delta i andre selskap og investering i aksjer i datterselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 59,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 59,000
▼ −10 %
Operating profit
NOK 18,000
▼ −45 %
Equity
NOK 875,000
▲ +4 %
Est. value
NOK 521,000

Financial health · 2025

Liquidity
21.46
Very good
Current assets ÷ current liabilities
Profitability
12.6%
Good
Return on total assets
Solidity
96.5%
Very good
Equity as a share of total capital

Who owns ATYS AS?

ATYS AS
NOK 59,000 rev. · NOK 18,000 profit

ATYS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ATYS AS own?

ATYS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ATYS AS

Who owns ATYS AS?

Bjørn Are Nygård is the largest registered owner, with 100.0%.

What is the revenue of ATYS AS?

ATYS AS had revenue of NOK 59,000 in 2025.

Who is the general manager of ATYS AS?

Bjørn Are Nygård is registered as general manager of ATYS AS.

Where is ATYS AS based?

ATYS AS has its business address in Kleppe.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.