biztrac. BETA
COMPANY REGISTER PROFILE
827259292 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery

ATAVOLA AS

Org. no. 827259292 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 222,000
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 30,000

ATAVOLA AS is registered as a limited company in Oslo, Oslo with organisation number 827259292. The business is classified under retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery (NACE 47.553). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med kjøkkenutstyr, glass og porselen, og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 222,000 in operating profit.

Former names: NYE ATAVOLA AS

Key figures · 2025

Revenue
NOK 6.0m
▼ −11 %
Operating profit
NOK 222,000
▼ −26 %
Equity
NOK 1.4m
▲ +6 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
11.45
Very good
Current assets ÷ current liabilities
Profitability
7.9%
Satisfactory
Return on total assets
Solidity
47.2%
Very good
Equity as a share of total capital

Who owns ATAVOLA AS?

ATAVOLA AS
NOK 6.0m rev. · NOK 222,000 profit

ATAVOLA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATAVOLA AS

Who owns ATAVOLA AS?

FOURIER AS is the largest registered owner, with 100.0%.

What is the revenue of ATAVOLA AS?

ATAVOLA AS had revenue of NOK 6.0m in 2025.

Who is the general manager of ATAVOLA AS?

Brit Bostad is registered as general manager of ATAVOLA AS.

Where is ATAVOLA AS based?

ATAVOLA AS has its business address in Oslo.

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.