BIZTRAC BETA
Translation and interpretation activities

ACCENTIA AS

Org. no. 929148312 Limited company (AS) Kongsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 778,000
Operating profit NOK 134,000
Equity NOK 40,000
Incorporated 2022
Share capital NOK 30,000

ACCENTIA AS is registered as a limited company in Kongsberg, Buskerud with organisation number 929148312. The business is classified under translation and interpretation activities (NACE 74.300). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oversettelse, språkvask, korrektur, tolking, translatørtjenester og undervisning, samt dertil naturlig tilhørende virksomhet, kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 778,000 in revenue and NOK 134,000 in operating profit.

Key figures · 2025

Revenue
NOK 778,000
Operating profit
NOK 134,000
Equity
NOK 40,000
Est. value
NOK 431,000

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.6%
Weak
Equity as a share of total capital

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

Who owns ACCENTIA AS?

KEVIN MICHAEL JOHN QUIRK
ACCENTIA AS
NOK 778,000 rev. · NOK 134,000 profit

ACCENTIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ACCENTIA AS

Who owns ACCENTIA AS?

KEVIN MICHAEL JOHN QUIRK is the largest registered owner, with 100.0%.

What is the revenue of ACCENTIA AS?

ACCENTIA AS had revenue of NOK 778,000 in 2025.

Who is the general manager of ACCENTIA AS?

Kevin Michael John Quirk is registered as general manager of ACCENTIA AS.

Where is ACCENTIA AS based?

ACCENTIA AS has its business address in Skollenborg.

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.