BIZTRAC BETA
Roofing activities

AKBLIKK AS

Org. no. 913412621 Limited company (AS) Arendal Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 732,000
Equity NOK 1.5m
Incorporated 2014
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AKBLIKK AS is registered as a limited company in Arendal, Agder with organisation number 913412621. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2014 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon av beslag for engrosmarkedet, blikkenslagervirksomhet, samt annet som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 732,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 732,000
Equity
NOK 1.5m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns AKBLIKK AS?

JT BERGTUN AS
AKBLIKK AS
NOK 6.9m rev. · NOK 732,000 profit

AKBLIKK AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AKBLIKK AS er morselskap for 3 datterselskaper:

Frequently asked questions about AKBLIKK AS

Who owns AKBLIKK AS?

JT BERGTUN AS is the largest registered owner, with 100.0%.

What is the revenue of AKBLIKK AS?

AKBLIKK AS had revenue of NOK 6.9m in 2025.

Who is the general manager of AKBLIKK AS?

Trygve Bergtun is registered as general manager of AKBLIKK AS.

Where is AKBLIKK AS based?

AKBLIKK AS has its business address in Arendal.

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.