biztrac. BETA
COMPANY REGISTER PROFILE
812351362 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BERVIKÅSEN BOLIGFELT AS

Org. no. 812351362 Limited company (AS) Skien Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −151,000
Incorporated 2013
Share capital NOK 600,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−151k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

BERVIKÅSEN BOLIGFELT AS is registered as a limited company in Skien, Telemark with organisation number 812351362. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 600,000, divided into 100 shares. The company's stated purpose is: “Utvikling av tomteområde for salg av tomter og boliger, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −9,000
▼ −41 %
Equity
NOK −151,000
▼ −6 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-2567.2%
Not satisfactory
Return on total assets
Solidity
-540792.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BERVIKÅSEN BOLIGFELT AS?

BERVIKÅSEN BOLIGFELT AS
· NOK −9,000 profit

BERVIKÅSEN BOLIGFELT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERVIKÅSEN BOLIGFELT AS

Who owns BERVIKÅSEN BOLIGFELT AS?

TELEMARKHUS HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of BERVIKÅSEN BOLIGFELT AS?

Magnar Sten Larsen is registered as general manager of BERVIKÅSEN BOLIGFELT AS.

Where is BERVIKÅSEN BOLIGFELT AS based?

BERVIKÅSEN BOLIGFELT 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.