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

EK BYGG OG INVEST AS

Org. no. 934547551 Limited company (AS) Rælingen Incorporated 2024 Active
Revenue 2025 NOK 1.5m
Operating profit NOK 159,000
Equity NOK 303,000
Incorporated 2024
Share capital NOK 30,000

EK BYGG OG INVEST AS is registered as a limited company in Rælingen, Akershus with organisation number 934547551. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring av bygg og investering i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +214 %
Operating profit
NOK 159,000
▼ −59 %
Equity
NOK 303,000
▼ −7 %
Est. value
NOK 754,000

Financial health · 2025

Liquidity
2.12
Very good
Current assets ÷ current liabilities
Profitability
25.8%
Very good
Return on total assets
Solidity
52.9%
Very good
Equity as a share of total capital

Who owns EK BYGG OG INVEST AS?

EK BYGG OG INVEST AS
NOK 1.5m rev. · NOK 159,000 profit

EK BYGG OG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EK BYGG OG INVEST AS

Who owns EK BYGG OG INVEST AS?

Espen Kristoffersen is the largest registered owner, with 100.0%.

What is the revenue of EK BYGG OG INVEST AS?

EK BYGG OG INVEST AS had revenue of NOK 1.5m in 2025.

Who is the general manager of EK BYGG OG INVEST AS?

Espen Kristoffersen is registered as general manager of EK BYGG OG INVEST AS.

Where is EK BYGG OG INVEST AS based?

EK BYGG OG INVEST AS has its business address in Fjerdingby.

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.