BIZTRAC BETA
COMPANY REGISTER PROFILE
876820722 ORG. NO. 10 SECTIONS
Active UPDATED 02.09.2026
Combined facilities support activities

DRAMMEN EIENDOM KF

Org. no. 876820722 Municipal business enterprise (KF) Drammen Incorporated 1996 Active
Ownership graph ↗
Incorporated 1996
Employees 146

DRAMMEN EIENDOM KF is registered as a municipal business enterprise in Drammen, Buskerud with organisation number 876820722. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 1996 and has 146 registered employees. The company's stated purpose is: “Eie, forvalte og utvikle kommunens bygnings- og eiendomsmasse etter forretningsmessige prinsipper. Ivareta kommunens byggeherrefunksjon. Være kommunens kompetansesenter innen leie av lokaler.”.

Former names: DRAMMEN KOMMUNE DRAMMEN EIENDOM KB, DRAMMEN EIENDOM KB

Who owns DRAMMEN EIENDOM KF?

No shareholders are registered for DRAMMEN EIENDOM KF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does DRAMMEN EIENDOM KF own?

DRAMMEN EIENDOM KF holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DRAMMEN EIENDOM KF

Who is the general manager of DRAMMEN EIENDOM KF?

Gjermund Riise Brekke is registered as general manager of DRAMMEN EIENDOM KF.

Where is DRAMMEN EIENDOM KF based?

DRAMMEN EIENDOM KF has its business address in Drammen.

Property

Business address Hans Kiærs gate 1E, 3041 Drammen
Cadastral unit 3301-111/246/0/0
Building Annen lagerbygning · 1 unit

10 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.