BIZTRAC BETA
Rental and operating of own or leased real estate

KOPPANGVEIEN 18 AS

Org. no. 926384678 Limited company (AS) Åmot Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 3.1m
Equity NOK 6.8m
Incorporated 2020
Share capital NOK 46,000

KOPPANGVEIEN 18 AS is registered as a limited company in Åmot, Innlandet with organisation number 926384678. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 46,000, divided into 15 shares. The company's stated purpose is: “Å eie og drive utleie av fast eiendom og maskiner samt eie aksjer eller andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 3.1m
Equity
NOK 6.8m
Est. value
NOK 11.1m

Financial health · 2024

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

Who owns KOPPANGVEIEN 18 AS?

TOM RØDSBAKKEN
KOPPANGVEIEN 18 AS
NOK 3.4m rev. · NOK 3.1m profit

KOPPANGVEIEN 18 AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KOPPANGVEIEN 18 AS own?

KOPPANGVEIEN 18 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KOPPANGVEIEN 18 AS

Who owns KOPPANGVEIEN 18 AS?

TOM RØDSBAKKEN is the largest registered owner, with 46.7%.

What is the revenue of KOPPANGVEIEN 18 AS?

KOPPANGVEIEN 18 AS had revenue of NOK 3.4m in 2024.

Who is the general manager of KOPPANGVEIEN 18 AS?

Tom Rødsbakken is registered as general manager of KOPPANGVEIEN 18 AS.

Where is KOPPANGVEIEN 18 AS based?

KOPPANGVEIEN 18 AS has its business address in Rena.

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.