BIZTRAC BETA
Accounting and bookkeeping

ALFA OMEGA REGNSKAP OG RÅDGIVNING AS

Org. no. 989286390 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.6m
Equity NOK 1.1m
Incorporated 2006
Share capital NOK 30,000

ALFA OMEGA REGNSKAP OG RÅDGIVNING AS is registered as a limited company in Bergen, Vestland with organisation number 989286390. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Regnskapsføring og økonomisk rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.6m
Equity
NOK 1.1m
Est. value
NOK 5.7m

Financial health · 2024

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns ALFA OMEGA REGNSKAP OG RÅDGIVNING AS?

NINA HORNÆS HANSEN
ALFA OMEGA REGNSKAP OG RÅDGIVNING AS
NOK 3.1m rev. · NOK 1.6m profit

ALFA OMEGA REGNSKAP OG RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALFA OMEGA REGNSKAP OG RÅDGIVNING AS

Who owns ALFA OMEGA REGNSKAP OG RÅDGIVNING AS?

NINA HORNÆS HANSEN is the largest registered owner, with 100.0%.

What is the revenue of ALFA OMEGA REGNSKAP OG RÅDGIVNING AS?

ALFA OMEGA REGNSKAP OG RÅDGIVNING AS had revenue of NOK 3.1m in 2024.

Who is the general manager of ALFA OMEGA REGNSKAP OG RÅDGIVNING AS?

Dag Arild Hansen is registered as general manager of ALFA OMEGA REGNSKAP OG RÅDGIVNING AS.

Where is ALFA OMEGA REGNSKAP OG RÅDGIVNING AS based?

ALFA OMEGA REGNSKAP OG RÅDGIVNING AS has its business address in Bønes.

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.