biztrac. BETA
COMPANY REGISTER PROFILE
913892852 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of insurance agents and brokers

FORSIKRING1 AS

Org. no. 913892852 Limited company (AS) Leirfjord Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 1.1m
Equity NOK 1.1m
Incorporated 2014
Share capital NOK 30,000

FORSIKRING1 AS is registered as a limited company in Leirfjord, Nordland with organisation number 913892852. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av forsikringsprodukter samt det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
▲ +5 %
Operating profit
NOK 1.1m
▲ +37 %
Equity
NOK 1.1m
▲ +19 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
45.9%
Very good
Return on total assets
Solidity
37.5%
Good
Equity as a share of total capital

Who owns FORSIKRING1 AS?

FORSIKRING1 AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FORSIKRING1 AS own?

FORSIKRING1 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FORSIKRING1 AS

Who owns FORSIKRING1 AS?

Kjell Øystein Pedersen is the largest registered owner, with 46.7%.

What is the revenue of FORSIKRING1 AS?

FORSIKRING1 AS had revenue of NOK 6.5m in 2025.

Who is the general manager of FORSIKRING1 AS?

Kjell Øystein Pedersen is registered as general manager of FORSIKRING1 AS.

Where is FORSIKRING1 AS based?

FORSIKRING1 AS has its business address in Leirfjord.

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

Report a problem

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