BIZTRAC BETA
COMPANY REGISTER PROFILE
992204710 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

AMROD AS

Org. no. 992204710 Limited company (AS) Vefsn Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 224,000
Operating profit NOK 34,000
Equity NOK 145,000
Incorporated 2007
Share capital NOK 500,000

AMROD AS is registered as a limited company in Vefsn, Nordland with organisation number 992204710. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2007. Registered share capital is NOK 500,000, divided into 1000000 shares. The company's stated purpose is: “Fremstilling og salg av ingeniørtjenester og andre aktiviteter som faller naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 224,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 224,000
Operating profit
NOK 34,000
Equity
NOK 145,000
Est. value
NOK 167,000

Financial health · 2025

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

Who owns AMROD AS?

LEIF STÅLE KJØNNÅS
AMROD AS
NOK 224,000 rev. · NOK 34,000 profit

AMROD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMROD AS

Who owns AMROD AS?

LEIF STÅLE KJØNNÅS is the largest registered owner, with 100.0%.

What is the revenue of AMROD AS?

AMROD AS had revenue of NOK 224,000 in 2025.

Who is the general manager of AMROD AS?

Leif Ståle Kjønnås is registered as general manager of AMROD AS.

Where is AMROD AS based?

AMROD AS has its business address in Mosjøen.

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.