BIZTRAC BETA
Construction of residential and non-residential buildings

TØMRERFIRMA RUNE OLSEN AS

Org. no. 886607342 Limited company (AS) Halden Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 386,000
Equity NOK 1.1m
Incorporated 2004
Share capital NOK 100,000

TØMRERFIRMA RUNE OLSEN AS is registered as a limited company in Halden, Østfold with organisation number 886607342. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tømrer og byggevirksomhet, kjøp, salg og utvikling av eiendomsprosjekter, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 386,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 386,000
Equity
NOK 1.1m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns TØMRERFIRMA RUNE OLSEN AS?

RUNE OLSEN
TØMRERFIRMA RUNE OLSEN AS
NOK 8.1m rev. · NOK 386,000 profit

TØMRERFIRMA RUNE OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRERFIRMA RUNE OLSEN AS

Who owns TØMRERFIRMA RUNE OLSEN AS?

RUNE OLSEN is the largest registered owner, with 100.0%.

What is the revenue of TØMRERFIRMA RUNE OLSEN AS?

TØMRERFIRMA RUNE OLSEN AS had revenue of NOK 8.1m in 2024.

Who is the general manager of TØMRERFIRMA RUNE OLSEN AS?

Rune Olsen is registered as general manager of TØMRERFIRMA RUNE OLSEN AS.

Where is TØMRERFIRMA RUNE OLSEN AS based?

TØMRERFIRMA RUNE OLSEN AS has its business address in Halden.

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.