BIZTRAC BETA
Development of building projects

LITLAFJELL UTBYGGING AS

Org. no. 895690082 Limited company (AS) Bergen Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 198,000
Operating profit NOK 156,000
Equity NOK −1.6m
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).

LITLAFJELL UTBYGGING AS is registered as a limited company in Bergen, Vestland with organisation number 895690082. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Næringsdrift, i hovedsak kjøp og salg av fast eiendom og alt hva herved er forbundet. Investeringsvirksomhet og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 198,000 in revenue and NOK 156,000 in operating profit.

Key figures · 2024

Revenue
NOK 198,000
Operating profit
NOK 156,000
Equity
NOK −1.6m
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-435.1%
Weak
Equity as a share of total capital

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

Who owns LITLAFJELL UTBYGGING AS?

SECUNDUS AS
LITLAFJELL UTBYGGING AS
NOK 198,000 rev. · NOK 156,000 profit

LITLAFJELL UTBYGGING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LITLAFJELL UTBYGGING AS

Who owns LITLAFJELL UTBYGGING AS?

SECUNDUS AS is the largest registered owner, with 50.0%.

What is the revenue of LITLAFJELL UTBYGGING AS?

LITLAFJELL UTBYGGING AS had revenue of NOK 198,000 in 2024.

Where is LITLAFJELL UTBYGGING AS based?

LITLAFJELL UTBYGGING AS has its business address in Bergen.

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.