BIZTRAC BETA
Rental and operating of own or leased real estate

PORSGRUNNSVEIEN 304 AS

Org. no. 961866855 Limited company (AS) Skien Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 1.0m
Equity NOK 2.7m
Incorporated 1991
Share capital NOK 150,000

PORSGRUNNSVEIEN 304 AS is registered as a limited company in Skien, Telemark with organisation number 961866855. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 150,000, divided into 300 shares. The company's stated purpose is: “Drift av, samt kjøp og salg av fast eiendom etc. og hva hermed står i forbindelse. Selskapet kan også ved aksjetegning eller på annen måte delta i annen næring.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 1.0m
Equity
NOK 2.7m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns PORSGRUNNSVEIEN 304 AS?

KNATTEN SKI AS
PORSGRUNNSVEIEN 304 AS
NOK 1.5m rev. · NOK 1.0m profit

PORSGRUNNSVEIEN 304 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PORSGRUNNSVEIEN 304 AS

Who owns PORSGRUNNSVEIEN 304 AS?

KNATTEN SKI AS is the largest registered owner, with 50.0%.

What is the revenue of PORSGRUNNSVEIEN 304 AS?

PORSGRUNNSVEIEN 304 AS had revenue of NOK 1.5m in 2025.

Who is the general manager of PORSGRUNNSVEIEN 304 AS?

Stian Numme is registered as general manager of PORSGRUNNSVEIEN 304 AS.

Where is PORSGRUNNSVEIEN 304 AS based?

PORSGRUNNSVEIEN 304 AS has its business address in Skien.

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.