BIZTRAC BETA
Civil engineering activities

ELVEMO TAKST AS

Org. no. 933729362 Limited company (AS) Storfjord Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 298,000
Equity NOK 118,000
Incorporated 2024
Share capital NOK 30,000

ELVEMO TAKST AS is registered as a limited company in Storfjord, Troms with organisation number 933729362. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Taksering og utarbeidelse av andre rapporter vedrørende fast eiendom herunder byggeteknisk rådgivning, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 298,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 298,000
Equity
NOK 118,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns ELVEMO TAKST AS?

BJØRNAR ELVEMO
ELVEMO TAKST AS
NOK 1.8m rev. · NOK 298,000 profit

ELVEMO TAKST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELVEMO TAKST AS own?

ELVEMO TAKST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELVEMO TAKST AS

Who owns ELVEMO TAKST AS?

BJØRNAR ELVEMO is the largest registered owner, with 100.0%.

What is the revenue of ELVEMO TAKST AS?

ELVEMO TAKST AS had revenue of NOK 1.8m in 2024.

Who is the general manager of ELVEMO TAKST AS?

Bjørnar Elvemo is registered as general manager of ELVEMO TAKST AS.

Where is ELVEMO TAKST AS based?

ELVEMO TAKST AS has its business address in Oteren.

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.