BIZTRAC BETA
Joinery installation

PORTSENTERET AS

Org. no. 996390659 Limited company (AS) Lier Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 12.6m
Operating profit NOK 36,000
Equity NOK 602,000
Incorporated 2010
Share capital NOK 100,000

Signals

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

PORTSENTERET AS is registered as a limited company in Lier, Buskerud with organisation number 996390659. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Oppføring og vedlikehold av bygninger samt kjøp og salg av materiell i denne forbindelse, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.6m in revenue and NOK 36,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.6m
Operating profit
NOK 36,000
Equity
NOK 602,000
Est. value
NOK 365,000

Financial health · 2024

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

Who owns PORTSENTERET AS?

N&F HOLDING AS
PORTSENTERET AS
NOK 12.6m rev. · NOK 36,000 profit

PORTSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PORTSENTERET AS

Who owns PORTSENTERET AS?

N&F HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PORTSENTERET AS?

PORTSENTERET AS had revenue of NOK 12.6m in 2024.

Who is the general manager of PORTSENTERET AS?

Kjetil Fossen is registered as general manager of PORTSENTERET AS.

Where is PORTSENTERET AS based?

PORTSENTERET AS has its business address in Lierskogen.

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.