biztrac. BETA
COMPANY REGISTER PROFILE
927941058 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Service activities incidental to air transportation

ANONA AS

Org. no. 927941058 Limited company (AS) Skien Incorporated 2021 Active
Revenue 2025 NOK 23.6m
Operating profit NOK −549,000
Equity NOK −89,000
Incorporated 2021
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−89k kr).

ANONA AS is registered as a limited company in Skien, Telemark with organisation number 927941058. The business is classified under service activities incidental to air transportation (NACE 52.230). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Flymegling.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.6m in revenue and NOK −549,000 in operating profit.

Former names: BYGG HOS AS

Key figures · 2025

Revenue
NOK 23.6m
▲ +31 %
Operating profit
NOK −549,000
▼ −259 %
Equity
NOK −89,000
▼ −129 %

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
-20.2%
Not satisfactory
Return on total assets
Solidity
-6.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ANONA AS?

ANONA AS
NOK 23.6m rev. · NOK −549,000 profit

ANONA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANONA AS

Who owns ANONA AS?

ANONA GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of ANONA AS?

ANONA AS had revenue of NOK 23.6m in 2025.

Who is the general manager of ANONA AS?

Andreas Kleppe Oterholt is registered as general manager of ANONA AS.

Where is ANONA AS based?

ANONA AS has its business address in Skien.

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.