biztrac. BETA
COMPANY REGISTER PROFILE
976553136 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

FOSSKOLLEN UTBYGGINGSSELSKAP AS

Org. no. 976553136 Limited company (AS) Tønsberg Incorporated 1996 Active
Ownership graph ↗
Operating profit NOK 611,000
Equity NOK 2.3m
Incorporated 1996
Share capital NOK 794,000

FOSSKOLLEN UTBYGGINGSSELSKAP AS is registered as a limited company in Tønsberg, Vestfold with organisation number 976553136. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1996. Registered share capital is NOK 794,000, divided into 600 shares. The company's stated purpose is: “Selskapets formål er utbygging av eiendom gjennom blant annet kjøp av grunn, opparbeidelse av teknisk anlegg, oppdeling i byggetomter og salg av boligtomter og boliger samt alt som naturlig står i forbindelse med dette. ”.

Former names: LUKEÅSEN UTBYGGINGSSELSKAP AS

Key figures · 2025

Operating profit
NOK 611,000
▲ +345 %
Equity
NOK 2.3m
▲ +32 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
87.1%
Very good
Equity as a share of total capital

Who owns FOSSKOLLEN UTBYGGINGSSELSKAP AS?

FOSSKOLLEN UTBYGGINGSSELSKAP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOSSKOLLEN UTBYGGINGSSELSKAP AS

Who owns FOSSKOLLEN UTBYGGINGSSELSKAP AS?

Jan Ole Backe Johannessen is the largest registered owner, with 33.3%.

Who is the general manager of FOSSKOLLEN UTBYGGINGSSELSKAP AS?

Runar Ommedal is registered as general manager of FOSSKOLLEN UTBYGGINGSSELSKAP AS.

Where is FOSSKOLLEN UTBYGGINGSSELSKAP AS based?

FOSSKOLLEN UTBYGGINGSSELSKAP AS has its business address in Våle.

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.