BIZTRAC BETA
Roofing activities

KOLBJØRN PEDERSEN EFTF AS

Org. no. 898780422 Limited company (AS) Ørland Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 152,000
Operating profit NOK −30,000
Equity NOK 120,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).

KOLBJØRN PEDERSEN EFTF AS is registered as a limited company in Ørland, Trøndelag with organisation number 898780422. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreperenør virksomhet innen taktekking og blikenslager.”. The most recent filed accounts, for the 2025 financial year, show NOK 152,000 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 152,000
Operating profit
NOK −30,000
Equity
NOK 120,000
Est. value
NOK 105,000

Financial health · 2025

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

Who owns KOLBJØRN PEDERSEN EFTF AS?

ROGER PETTERSEN
KOLBJØRN PEDERSEN EFTF AS
NOK 152,000 rev. · NOK −30,000 profit

KOLBJØRN PEDERSEN EFTF AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOLBJØRN PEDERSEN EFTF AS

Who owns KOLBJØRN PEDERSEN EFTF AS?

ROGER PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of KOLBJØRN PEDERSEN EFTF AS?

KOLBJØRN PEDERSEN EFTF AS had revenue of NOK 152,000 in 2025.

Who is the general manager of KOLBJØRN PEDERSEN EFTF AS?

Roger Pettersen is registered as general manager of KOLBJØRN PEDERSEN EFTF AS.

Where is KOLBJØRN PEDERSEN EFTF AS based?

KOLBJØRN PEDERSEN EFTF AS has its business address in Brekstad.

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.