BIZTRAC BETA
Site preparation

EKKO SERVICE AS

Org. no. 886296762 Limited company (AS) Ringsaker Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 6.1m
Operating profit NOK 397,000
Equity NOK 5.8m
Incorporated 2003
Employees 8
Share capital NOK 100,000

EKKO SERVICE AS is registered as a limited company in Ringsaker, Innlandet with organisation number 886296762. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2003 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Gravemaskinarbeide, maskinkjøring, vedproduksjon, gressklipping, snørydding, vaktmesteroppgaver, import og eksport av biler, båter, maskiner og utstyr, utleie av arbeidskraft, investering i bygg og andre selskaper og hva dermed hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.1m in revenue and NOK 397,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.1m
Operating profit
NOK 397,000
Equity
NOK 5.8m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns EKKO SERVICE AS?

GUDMUND TVEDT GRÆSBY
EKKO SERVICE AS
NOK 6.1m rev. · NOK 397,000 profit

EKKO SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EKKO SERVICE AS

Who owns EKKO SERVICE AS?

GUDMUND TVEDT GRÆSBY is the largest registered owner, with 100.0%.

What is the revenue of EKKO SERVICE AS?

EKKO SERVICE AS had revenue of NOK 6.1m in 2024.

Who is the general manager of EKKO SERVICE AS?

Gudmund Tvedt Græsby is registered as general manager of EKKO SERVICE AS.

Where is EKKO SERVICE AS based?

EKKO SERVICE AS has its business address in Furnes.

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.