BIZTRAC BETA
Construction of residential and non-residential buildings

2 ROM OG KJØKKEN AS

Org. no. 914085292 Limited company (AS) Vestre Toten Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 338,000
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 30,000

2 ROM OG KJØKKEN AS is registered as a limited company in Vestre Toten, Innlandet with organisation number 914085292. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring og utleie av boligbygg, samt alle oppgaver naturlig forbundet med dette. Selskapet skal også kunne investere i verdipapirer og delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 338,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 338,000
Equity
NOK 1.5m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns 2 ROM OG KJØKKEN AS?

TORE HAGEN
2 ROM OG KJØKKEN AS
NOK 3.6m rev. · NOK 338,000 profit

2 ROM OG KJØKKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 2 ROM OG KJØKKEN AS

Who owns 2 ROM OG KJØKKEN AS?

TORE HAGEN is the largest registered owner, with 50.0%.

What is the revenue of 2 ROM OG KJØKKEN AS?

2 ROM OG KJØKKEN AS had revenue of NOK 3.6m in 2024.

Who is the general manager of 2 ROM OG KJØKKEN AS?

Tore Hagen is registered as general manager of 2 ROM OG KJØKKEN AS.

Where is 2 ROM OG KJØKKEN AS based?

2 ROM OG KJØKKEN AS has its business address in Bøverbru.

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.