BIZTRAC BETA
Joinery installation

EKRE BYGGSERVICE AS

Org. no. 925582816 Limited company (AS) Lillehammer Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK −21,000
Equity NOK 120,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

EKRE BYGGSERVICE AS is registered as a limited company in Lillehammer, Innlandet with organisation number 925582816. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Snekkervirksomhet, herunder oppføring av bygg, tilbygg, restaurering og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK −21,000
Equity
NOK 120,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns EKRE BYGGSERVICE AS?

LARS OTTAR FLITTIE EKRE
EKRE BYGGSERVICE AS
NOK 4.5m rev. · NOK −21,000 profit

EKRE BYGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EKRE BYGGSERVICE AS

Who owns EKRE BYGGSERVICE AS?

LARS OTTAR FLITTIE EKRE is the largest registered owner, with 100.0%.

What is the revenue of EKRE BYGGSERVICE AS?

EKRE BYGGSERVICE AS had revenue of NOK 4.5m in 2025.

Who is the general manager of EKRE BYGGSERVICE AS?

Lars Ottar Flittie Ekre is registered as general manager of EKRE BYGGSERVICE AS.

Where is EKRE BYGGSERVICE AS based?

EKRE BYGGSERVICE AS has its business address in Lillehammer.

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.