BIZTRAC BETA
Construction of residential and non-residential buildings

TØMRERMESTER KÅRE ELIASSEN AS

Org. no. 915230547 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 112,000
Equity NOK 259,000
Incorporated 2015
Share capital NOK 30,000

TØMRERMESTER KÅRE ELIASSEN AS is registered as a limited company in Asker, Akershus with organisation number 915230547. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring av bygninger, restaurering og snekring.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 112,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 112,000
Equity
NOK 259,000
Est. value
NOK 470,000

Financial health · 2024

Liquidity
2.59
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
64.4%
Very good
Equity as a share of total capital

Who owns TØMRERMESTER KÅRE ELIASSEN AS?

KÅRE ELIASSEN
TØMRERMESTER KÅRE ELIASSEN AS
NOK 1.4m rev. · NOK 112,000 profit

TØMRERMESTER KÅRE ELIASSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRERMESTER KÅRE ELIASSEN AS

Who owns TØMRERMESTER KÅRE ELIASSEN AS?

KÅRE ELIASSEN is the largest registered owner, with 100.0%.

What is the revenue of TØMRERMESTER KÅRE ELIASSEN AS?

TØMRERMESTER KÅRE ELIASSEN AS had revenue of NOK 1.4m in 2024.

Who is the general manager of TØMRERMESTER KÅRE ELIASSEN AS?

Kåre Eliassen is registered as general manager of TØMRERMESTER KÅRE ELIASSEN AS.

Where is TØMRERMESTER KÅRE ELIASSEN AS based?

TØMRERMESTER KÅRE ELIASSEN AS has its business address in Borgen.

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.