BIZTRAC BETA
Activities of insurance agents and brokers

DRAMMEN FORSIKRING AS

Org. no. 916917015 Limited company (AS) Drammen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 175,000
Equity NOK 462,000
Incorporated 2016
Employees 15
Share capital NOK 100,000

DRAMMEN FORSIKRING AS is registered as a limited company in Drammen, Buskerud with organisation number 916917015. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2016 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og rådgivning i forbindelse med forsikringsprodukter samt produkter som hører naturlig under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 175,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 175,000
Equity
NOK 462,000
Est. value
NOK 709,000

Financial health · 2024

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.1%
Good
Equity as a share of total capital

Who owns DRAMMEN FORSIKRING AS?

CLAUS ANDRE BJØRNSEN
DRAMMEN FORSIKRING AS
NOK 4.9m rev. · NOK 175,000 profit

DRAMMEN FORSIKRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRAMMEN FORSIKRING AS

Who owns DRAMMEN FORSIKRING AS?

CLAUS ANDRE BJØRNSEN is the largest registered owner, with 100.0%.

What is the revenue of DRAMMEN FORSIKRING AS?

DRAMMEN FORSIKRING AS had revenue of NOK 4.9m in 2024.

Who is the general manager of DRAMMEN FORSIKRING AS?

Claus Andre Bjørnsen is registered as general manager of DRAMMEN FORSIKRING AS.

Where is DRAMMEN FORSIKRING AS based?

DRAMMEN FORSIKRING AS has its business address in Drammen.

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.